System and method for controlling a call processing system

ABSTRACT

A system and method for managing a call processing system includes a signaling interface that receives and processes message parameters and call signaling and transmits and receives call signaling and message parameters to and from a call processor. A call processor processes call signaling to select connections for calls. An interworking unit interworks user communications between time division multiplex (TDM) connections and asynchronous transfer mode (ATM) connections. An ATM matrix connects user communications between ATM connections. A call process control system (CPCS) manages the call processing elements including the signaling interface, the call processor, the interworking unit, and the ATM matrix. The CPCS provides call management applications such as call trace, call tap, remote call control, accounting, configuration of the call processing elements, and interfacing between external devices and the call processing elements.

RELATED APPLICATIONS

Not Applicable

FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

MICROFICHE APPENDIX

Not Applicable

FIELD OF THE INVENTION

The present invention relates to the field of administration oftelecommunications call connecting management and transport devices.

BACKGROUND OF THE INVENTION

Broadband systems provide telecommunications providers with manybenefits, including greater bandwidth, more efficient use of bandwidth,and the ability to integrate voice, data, and video communications.These broadband systems provide callers with increased capabilities atlower costs.

The broadband systems may have multiple elements that operate togetherto connect calls. Some elements may process call signaling while otherelements make connections for calls. Alternately, a single element maybe used to both process call signaling and to make connections forcalls. In either system, there is a need for a system to provide formaintenance and administration of the elements. Such a system should becapable of providing the administration services for local or regionalelements. The system of the present invention provides theses needs.

SUMMARY OF THE INVENTION

The present invention comprises a system for administering callprocesses for a call. The system comprises a signaling processor adaptedto process call signaling. The system further comprises a managementsystem adapted to transmit configuration data to the signalingprocessor, to manage performance data associated with the call, and toremotely control a call processing application.

The present invention also comprises a system for managing a callprocess for a call. The system comprises a communication system adaptedto transfer a communication between an external device and the system.The system includes a remote call control system adapted to remotelycontrol a call processing application for the call. The system alsocomprises a fault management system adapted to manage fault data fromthe external device.

The present invention also is directed to a system for administering acall process for a call having call signaling and user communications.The system comprises a signaling processor adapted to process the callsignaling to select a connection for the call and to transmit a controlmessage designating the selected connection. The system furthercomprises a connection system adapted to receive the control message andto connect the user communications over the selected connection. Thesystem includes a management system that comprises a communicationsystem adapted to transfer a communication between the management systemand at least one of the signaling processor and the connection system.The management system includes a remote call control system adapted toremotely control a call processing application for the call. Themanagement system also comprises a fault management system adapted tomanage fault data from at least one of the signaling processor and theconnection system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a regional call process control system inaccordance with an embodiment of the present invention.

FIG. 2 is a block diagram of a call process control system with anexpanded call signaling and call processing system in accordance with anembodiment of the present invention.

FIG. 3 is a block diagram of an expanded call process control system inaccordance with an embodiment of the present invention.

FIG. 4 is a block diagram of a fault management system in accordancewith an embodiment of the present invention.

FIG. 5 is a block diagram of a remote call control system in accordancewith an embodiment of the present invention.

FIG. 6 is a block diagram of a historical data processing system with anoperational measurements system in accordance with an embodiment of thepresent invention.

FIG. 7 is a block diagram of an accounting control system in accordancewith an embodiment of the present invention.

FIG. 8 is a block diagram of a configuration management system inaccordance with an embodiment of the present invention.

FIG. 9 is a functional diagram of a controllable asynchronous transfermode matrix in accordance with the present invention.

FIG. 10 is a functional diagram of a controllable asynchronous transfermode matrix with time division multiplex capability in accordance withthe present invention.

FIG. 11 is a functional diagram of an asynchronous transfer modeinterworking unit for use with a synchronous optical network system inaccordance with the present invention.

FIG. 12 is a functional diagram of an asynchronous transfer modeinterworking unit for use with a synchronous digital hierarchy system inaccordance with the present invention.

FIG. 13 is a block diagram of a signaling processor constructed inaccordance with the present system.

FIG. 14 is a block diagram of a data structure having tables that areused in the signaling processor of FIG. 13.

FIG. 15 is a block diagram of additional tables that are used in thesignaling processor of FIG. 14.

FIG. 16 is a block diagram of additional tables that are used in thesignaling processor of FIG. 14.

FIG. 17 is a block diagram of additional tables that are used in thesignaling processor of FIG. 14.

FIG. 18 is a table diagram of a time division multiplex trunk circuittable used in the signaling processor of FIG. 14.

FIG. 19 is a table diagram of an asynchronous transfer mode trunkcircuit table used in the signaling processor of FIG. 14.

FIG. 20A is a table diagram of a trunk group table used in the signalingprocessor of FIG. 14.

FIG. 20B is a continuation table diagram of the trunk group table ofFIG. 20A.

FIG. 20C is a table diagram of a continuation of the trunk group tableof FIG. 20B.

FIG. 21 is a table diagram of a carrier table used in the signalingprocessor of FIG. 14.

FIG. 22 is a table diagram of an exception table used in the signalingprocessor of FIG. 14.

FIG. 23 is a table diagram of an originating line information table usedin the signaling processor of FIG. 14.

FIG. 24 is a table diagram of an automated number identification tableused in the signaling processor of FIG. 14.

FIG. 25 is a table diagram of a called number screening table used inthe signaling processor of FIG. 14.

FIG. 26 is a table diagram of a called number table used in thesignaling processor of FIG. 14.

FIG. 27 is a table diagram of a day of year table used in the signalingprocessor of FIG. 14.

FIG. 28 is a table diagram of a day of week table used in the signalingprocessor of FIG. 14.

FIG. 29 is a table diagram of a time of day table used in the signalingprocessor of FIG. 14.

FIG. 30 is a table diagram of a time zone table used in the signalingprocessor of FIG. 14.

FIG. 31 is a table diagram of a routing table used in the signalingprocessor of FIG. 14.

FIG. 32 is a table diagram of a trunk group class of service table usedin the signaling processor of FIG. 14.

FIG. 33 is a table diagram of a treatment table used in the signalingprocessor of FIG. 14.

FIG. 34 is a table diagram of an outgoing release table used in thesignaling processor of FIG. 14.

FIG. 35 is a table diagram of a percent control table used in thesignaling processor of FIG. 14.

FIG. 36 is a table diagram of a call rate table used in the signalingprocessor of FIG. 14.

FIG. 37 is a table diagram of a database services table used in thesignaling processor of FIG. 14.

FIG. 38A is a table diagram of a signaling connection control part tableused in the signaling processor of FIG. 14.

FIG. 38B is a continuation table diagram of the signaling connectioncontrol part table of FIG. 38A.

FIG. 38C is a continuation table diagram of the signaling connectioncontrol part table of FIG. 38B.

FIG. 38D is a continuation table diagram of the signaling connectioncontrol part table of FIG. 38C.

FIG. 39 is a table diagram of an intermediate signaling networkidentification table used in the signaling processor of FIG. 14.

FIG. 40 is a table diagram of a transaction capabilities applicationpart table used in the signaling processor of FIG. 14.

FIG. 41 is a table diagram of a external echo canceller table used inthe signaling processor of FIG. 14.

FIG. 42 is a table diagram of an interworking unit used in the signalingprocessor of FIG. 14.

FIG. 43 is a table diagram of a controllable asynchronous transfer modematrix interface table used in the signaling processor of FIG. 14.

FIG. 44 is a table diagram of a controllable asynchronous transfer modematrix table used in the signaling processor of FIG. 14.

FIG. 45A is a table diagram of a site office table used in the signalingprocessor of FIG. 14.

FIG. 45B is a continuation table diagram of the site office table ofFIG. 45A.

FIG. 45C is a continuation table diagram of the site office table ofFIG. 45B.

FIG. 45D is a continuation table diagram of the site office table ofFIG. 45C.

FIG. 46A is a table diagram of an advanced intelligent network eventparameters table used in the signaling processor of FIG. 14.

FIG. 46B is a continuation table diagram of the advanced intelligentnetwork event parameters table of FIG. 46A.

FIG. 47 is a table diagram of a message mapping table used in thesignaling processor of FIG. 14.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Telecommunication systems have a number of communication devices inlocal exchange and interexchange environments that interact to providecall services to customers. Both traditional and intelligent network(IN) services and resources are used to process, route, or connect acall to a designated connection.

A call has user communications and call signaling. The usercommunications contain the caller's information, such as a voicecommunication or data communication, and they are transported over aconnection. Call signaling contains information that facilitates callprocessing, and it is communicated over a link. Call signaling, forexample, contains information describing the called number and thecalling number. Examples of call signaling are standardized signaling,such as signaling system #7 (SS7), C7, integrated services digitalnetwork (ISDN), and digital private network signaling system (DPNSS),which are based on ITU recommendation Q.931. A call can be connected toand from communication devices.

Connections are used to transport user communications and other deviceinformation between communication devices and between the elements anddevices of the system. The term “connection” as used herein means thetransmission media used to carry user communications between elements ofthe various telecommunications networks and systems. For example, aconnection could carry a user's voice, computer data, or othercommunication device data. A connection can be associated with eitherin-band communications or out-of-band communications.

Links are used to transport call signaling and control messages. Theterm “link” as used herein means a transmission media used to carry callsignaling and control messages. For example, a link would carry callsignaling or a device control message containing device instructions anddata. A link can carry, for example, out-of-band signaling such as thatused in SS7, C7, ISDN, DPNSS, B-ISDN, GR-303, or could be via local areanetwork (LAN), or data bus call signaling. A link can be, for example,an asynchronous transfer mode (ATM) adaptation layer 5 (AAL5) data link,UDP/IP, ethernet, DS0, or DS1. In addition, a link, as shown in thefigures, can represent a single physical link or multiple links, such asone link or a combination of links of ISDN, SS7, TCP/IP, or some otherdata link. The term “control message” as used herein means a control orsignaling message, a control or signaling instruction, or a control orsignaling signal, whether proprietary or standardized, that conveysinformation from one point to another.

FIG. 1 illustrates an exemplary embodiment of a call processing system102 of the present invention. The call processing system 102 has amanagement system, such as a call process control system (CPCS) 104,which is linked to a first signaling processor 106, a first connectionsystem 108, a second signaling processor 110, and a second connectionsystem 112.

The CPCS 104 is a management and administration system. The CPCS 104 isthe user interface and external systems interface into the signalingprocessors 106 and 110 and the connection systems 108 and 112. The CPCS104 serves as a collection point for call-associated data such as callprocessing and call routing data, logs, operational measurement data,alarms, statistical information, accounting information, and other calldata. The CPCS 104 maintains and processes this data for accountingsystems, alarm reporting systems, and other enterprise systems. The CPCS104 maintains a security firewall between the enterprise systems and theother elements of the call processing system 102, such as the signalingprocessors 106 and 110.

The CPCS 104 accepts call processing data, such as the translations,from operations systems and updates data in call processing tables inthe signaling processors 106 and 110. The CPCS 104 maintains a current,historical, and future view of the call processing tables. The CPCS 104also provides configuration data and control to the elements of the callprocessing system 102 including the signaling processors 106 and 110 andthe connection systems 108 and 112 and collects data from the elements.

In addition, the CPCS 104 provides for remote control of callprocessing, call processing applications, and other applications such ascall monitoring and call tapping at the signaling processor 106 and 110.The CPCS may be a local CPCS that services only elements of a localsignaling system or a regional CPCS that services elements of multiplesignaling systems. In the embodiment of FIG. 1, the CPCS 104 isillustrated as a regional CPCS.

The signaling processors 106 and 110 are signaling platforms that canreceive, process, and generate call signaling. Based on the processedcall signaling, the signaling processors 106 and 110 select processingoptions, services, or resources for the user communications and generateand transmit control messages that identify the communication device,processing option, service, or resource that is to be used. Thesignaling processors 106 and 110 also select virtual connections andcircuit-based connections for call routing and generate and transportcontrol messages that identify the selected connections. The signalingprocessors 106 and 110 can process various forms of signaling, includingISDN, GR-303, B-ISDN, SS7, and C7. A preferred signaling processor isdiscussed below.

The connection systems 108 and 112 make connections for calls. Theconnection systems 108 and 112 may interwork user communications toconnections or switch user communications between connections.Preferably, interworking occurs between time division multiplex (TDM)connections and asynchronous transfer mode (ATM) connections, andswitching occurs between ATM connections and other ATM connections andbetween TDM connections and other TDM connections. The connectionsystems 108 and 112 establish connections for user communications inresponse to control messages from the signaling processors 106 and 110,respectively.

FIG. 2 illustrates an exemplary embodiment of a call processing system102A of the present invention with an expanded call signaling and callprocessing system. The call processing system 102A of FIG. 2 comprisesthe CPCS 104 linked to a signaling interface 202, a call processor 204,an interworking unit 206, and an ATM matrix 208. In addition, anoperations system 210 is linked to the CPCS 104. Moreover, a firstcommunication device 212 and a second communication device 214 areconnected through connections 216 and 218 to the interworking unit 206and the ATM matrix 208, respectively. A connection 220 connects theinterworking unit 206 and the ATM matrix 208.

The signaling interface 202 receives, processes, and transmits callsignaling. The signaling interface 202 can obtain information from, andtransmit information to, a communication device. Such information may betransferred, for example, as a TCAP message in queries or responses oras other SS7 messages such as an initial address message (IAM). Thesignaling interface 202 also passes information to the call processor204 for processing and passes information from the call processor toother communication devices (not shown).

The call processor 204 is a signaling platform that can receive andprocess call signaling. The call processor 204 has data tables whichhave call connection data and which are used to process the callsignaling. Based on the processed call signaling, the call processor 204selects processing options, services, resources, or connections for theuser communications. The call processor 204 generates and transmitscontrol messages that identify the communication device, processingoption, service, or resource that is to receive call signaling or thatis be used in call connections or further call processing. The callprocessor 204 also selects virtual connections and circuit-basedconnections for routing of call signaling and connections for usercommunications and generates and transports control messages thatidentify the selected connections.

The call processor 204 transmits an enhanced circuit data block (ECDB)for each call process to the CPCS 104. The ECDB contains all of theinformation associated with the calls from the call signaling, includingthe call processor or switch, the calling number, the called number, thepath, the equipment used to connect the calls, and echo canceller data.An example of the information in the ECDB is the information containedin the call processing tables explained below. The CPCS 104 combines theinformation in the ECDB with fixed attributes, such as a name associatedwith a trunk group number for example, to create a call informationblock (CIB).

The interworking unit 206 interworks traffic between various protocols.Preferably, the interworking unit 206 interworks between ATM traffic andnon-ATM traffic, such as TDM traffic. The interworking unit 206 operatesin accordance with control messages received from the call processor204. These control messages typically are provided on a call-by-callbasis and typically identify an assignment between a DS0 and a VP/VC forwhich user communications are interworked. In some instances, theinterworking unit 206 may transport control messages which may includedata to the call processor 204.

The ATM matrix 208 is a controllable ATM matrix that establishesconnections in response to control messages received from the callprocessor 204. The ATM matrix 208 is able to interwork between ATMconnections and TDM connections. The ATM matrix 208 also cross connectsATM connections with other ATM connections. In addition, the ATM matrix208 can switch calls from TDM connections to other TDM connections. TheATM matrix 208 transmits and receives call signaling and usercommunications over the connections.

The operations system 210 transports translations for the callprocessing tables and other call-associated data to the CPCS 104. Inaddition, the operations system 210 accepts call-associated data fromthe CPCS 104. The operations system 210 comprises, for example, an alarmmonitoring system that receives alarm data, an operations report systemto receive trending data, an accounting system to receive accountingdata, or a configuration system to transmit call processing translationsor element configuration data to the CPCS 104. The operations system 210may comprise other elements.

The communication devices 212 and 214 comprise customer premisesequipment (CPE), a service platform, a switch, a remote digitalterminal, a cross connect, an interworking unit, an ATM gateway, or anyother device capable of initiating, handling, or terminating a call. CPEcan be, for example, a telephone, a computer, a facsimile machine, or aprivate branch exchange. A service platform can be, for example, anyenhanced computer platform that is capable of processing calls. A remotedigital terminal is a device that concentrates analog twisted pairs fromtelephones and other like devices and converts the analog signals to adigital format known as GR-303. An ATM gateway is a device that changesATM cell header VP/VC identifiers. The communication devices 212 and 214may be TDM based or ATM based. In the system of FIG. 2, preferably thefirst communication device 212 is TDM based, and the secondcommunication device 214 is ATM based.

The system of FIG. 2 operates as follows. Translations and other dataare transported to the CPCS 104 from the operations system 210 and fromother communications devices (not shown). In addition, the CPCS 104transports data to the operations system 210 and the othercommunications devices, if required.

The CPCS 104 processes the translations data and organizes the data intotables that are identical to call processing tables that are located inthe call processor 204. Then, the CPCS 104 data fills the callprocessing tables in the call processor 204. In addition, the CPCS 104transports data to any device or entity to which it is configured totransport the data. This data fill may be completed at any time, andupdates may be transported from the CPCS 104 to the call processor 204.

If any configuration of the signaling interface 202, the call processor204, the interworking unit 206, or the ATM matrix 208 is required by theCPCS 104, that configuration information is transmitted to theappropriate element. In addition, alarms from the signaling interface202, the call processor 204, the interworking unit 206, or the ATMmatrix 208 are transmitted to the CPCS 104.

The first communication device 212 transmits call signaling to thesignaling interface 202. The first communication device 212 transportsthe user communications to the interworking unit 206 over the connection216.

The signaling interface 202 receives the call signaling and processesthe call signaling to obtain call information elements. The signalinginterface 202 passes the call information elements to the call processor204.

The call processor 204 processes the call information elements to selectconnections 218 and 220 for the user communications. In this example,the selected connections 218 and 220 are each a VP/VC. However, in otherexamples, one or more of the selected connections may be a DS0 or otherTDM connection.

The call processor 204 sends a first control message to the interworkingunit 206 identifying the first selected connection 220 over which theuser communications will be interworked. The call processor 204 sends asecond control message to the ATM matrix 208 identifying the secondselected connection 218 over which the user communications will beconnected. In addition, the call processor 204 sends a setup ECDB to theCPCS 104.

The call processor 204 also sends call information elements to thesignaling interface 202 destined for another communication device, forexample, identifying the selected connection 218 over which the usercommunications are to be connected. The other communication device maybe, for example, another call processor or a switch which may handlecall signaling.

The signaling interface 202 receives the call information elements andprocesses them to obtain call signaling. In some instances, the controlmessage is converted to an SS7 message. The signaling interface 202transports the call signaling to the destination communication device.

The interworking unit 206 receives the user communications from thefirst communication device 212 over the connection 216 and the firstcontrol message from the call processor 204. The interworking unit 206interworks the user communications, between the connection 216 and theconnection 220 according to the first control message. In this example,the connection 216 is a TDM connection, such as a DS0.

The ATM matrix 208 receives the second control message from the callprocessor 204 and the user communications over the connection 220. TheATM matrix 208 connects the user communications to the connection 218designated in the control message. The second communication device 214receives the user communications over the connection 218.

When the call is completed, the call processor 204 transmits aterminating ECDB to the CPCS 104. The CPCS 104 configures the data inthe ECDBs with fixed attribute data to form the CIBs. The CPCS 104handles any additional alarm, configuration, or accounting function thatwas not handled during the call.

It will be appreciated that a call can be connected in the oppositedirection from the ATM side to the TDM side. Also, a call can beswitched from an ATM system to another ATM system or from a TDM systemto another TDM system. It will be appreciated that the call processor orswitch on the terminating side of the call also transmits ECDBs to theCPCS 104 during the call for setup and termination.

FIG. 3 illustrates an exemplary embodiment of a CPCS of the presentinvention. In the embodiment of FIG. 3, the CPCS 104 contains acommunication system 302, a human machine interface (HMI) 304, a faultmanagement system 306, a remote call control (RCC) 308, a performancemonitoring system, such as a raw history data system (RHDS) 310 and ahistorical data system 312, an accounting system 314, and aconfiguration management system (CMS) 316. The historical data system312 is linked to an operations reports system 318. The accounting system314 is linked to an external accounting system 320. The CMS 316 islinked to a service delivery platform (SDP) 322. The fault managementsystem 306 is linked to a network management system 324.

The communication system 302 transfers control messages with data andother communications between the other elements of the CPCS 104 and anexternal device, such as the signaling processor, including in thisexample the signaling interface 202 and the call processor 204, theconnection system, including in this example the interworking unit 206and the ATM matrix 208, or another communications device. As usedherein, an external device comprises a signaling processor, such as oneor more of a signaling interface and a call processor, a connectionsystem, such as one or more of an interworking unit and an ATM matrix,and a communications device, as described above, and other signalingprocessors or other connections systems. As used herein, a communicationincludes a control message.

The communication system 302 determines where the control messages areto be transmitted based upon the control message content and type andtransmits them thereto. The communication system 302 is fault tolerantfor reliability. An example of a messaging system standard that can beused as a basis for the communication system 302 is the common objectrequest broker architecture (CORBA) 2.0 specification standard developedby Object Management Group, Inc. (OMG, Inc.).

The HMI 304 allows a person to log onto the CPCS 104 and to manage datatables, such as the call processing tables, to review data tables in theCPCS, or to provide other maintenance services. Thus, the HMI 304 allowsaccess to the CPCS 104 for active call processing management and passivecall processing management.

The fault management system 306 manages alarm data, fault data, andother performance data from the signaling interface 202, the callprocessor 204, the interworking unit 206, and the ATM matrix 208.Initially, the signaling interface 202, the interworking unit 206, andthe ATM matrix 208 report the performance data to the call processor 204so that the processing tables can be updated. The call processor 204then forwards the performance data to the CPCS 104, and the faultmanagement system 306 configures the data in a reportable format. Thefault management system 306 insures that the CPCS 104 broadcasts thealarm, fault, and other performance data to the required supportsystems, such as the network management system 324. Parameters for therequired broadcast systems are configurable based upon an individualfault or alarm number or classification.

The RCC 308 is an autonomous management system that is used to provideservices for active calls and completed calls. The RCC 308 active callservices and completed call services functionality each includes calltracing, call tapping, call verification and queries, fraud detection,call testing, and call control management using, for example, skippingand gapping of calls.

The RCC 308 processes call information for calls that are in apersistent/active state. For example, when a call goes off-hook, thecall processor 204 sends a setup ECDB to the CPCS 104 which contains theoff-hook information as well as other call information about the call.When the call goes on-hook, a terminating ECDB is sent from the callprocessor 204 to the CPCS 104. The CPCS 104 has a list of active callsand a list of circuits that are busy. The RCC 308 uses this informationto determine how busy the call processor 204 is and to provide othercall control management services. Because this ECDB processing takesplace by the RCC 308 in the CPCS 104, processing time and space are notwasted in the call processor 204.

The RHDS 310 receives and stores the raw history for logs, alarms, andoperational measurements (OMs). The data is generated for five minuteintervals. The RHDS 310 transfers the data to the historical data system312 for processing.

The historical data system 312 provides decisional support for the rawhistory data which is stored in the RHDS 310. The historical data system312 receives data from the RHDS 310, extracts subsets of log data, alarmdata, and OM data, and formats it to usable events and OM measures forreporting to external systems, such as the operations reports system318, and for viewing.

The accounting system 314 processes the ECDBs with fixed attribute datato form the CIBs and uses the ECDBs and the CIBs to develop call detailrecords (CDRs). The accounting system 314 combines the CIBs to form theCDRs and then transmits the CDRs to the external accounting system 320.

The accounting system 314 accounting algorithms are based upon the callsignaling on an individual call by call basis. The actual call historyis reviewed and billing and other accounting applications are based onthe actual route and connections processed for the call. This avoidsuser data entry errors and translations data fill errors that wouldimpact accounting applications.

The CMS 316 is used to configure all elements of the call processingsystem, including the signaling interface 202, the call processor 204,the interworking unit 206, and the ATM matrix 208. The CMS 316 allows auser to define customer routing through the call processing tables.

The operations reports system 318 receives OM measures and otherreporting data from the CPCS 104. The operations reports system 318 thenforwards the reported data to appropriate centers for compilation and/ordistribution.

The external accounting system 320 receives accounting information, suchas CDRs, from the CPCS 104. The external accounting system 320 maycompile the data and forward it to appropriate centers for processingand distribution. An example of an accounting system is an enterprisesystem such as a merged call processor (MCP) system.

The SDP 322 provides product and service data to the CPCS 104. The SDP322 collects information from operations centers, such as fieldmaintenance systems, customer information systems, and other serviceorder entry platforms and forwards the data to the CPCS 104. The dataprovided to the CPCS 104 by the SDP 322 includes translations used todata fill the call processing tables and other network configurationdata.

The network management system 324 manages the fault data and the otherperformance data for the network. The network management system 324 islinked to other management systems and interfaces for other networks sothat performance data may be exchanged.

FIG. 4 illustrates an exemplary embodiment of a fault management system306 of the present invention. The fault management system 306 of FIG. 4has a CPCS site reporting control 402 with a site recovery database 404,a CPCS craft control 406 with a site equipment inventory database 408, asite craft control 410, and a regional craft control 412 with a CPCSequipment inventory database 414.

The CPCS site reporting control 402 controls which call processor orswitch reports reporting data, such as configuration data, callprocessing data, and other data, to a designated CPCS site. This controlis user configurable to allow for disaster planning if a CPCS site islost. The site recovery database 404 contains the data identifying whichcall processor or switch reports to the designated CPCS.

The CPCS craft control 406 provides the status and equipment inventoryof a CPCS site. If a hardware element at the CPCS site fails, it will beviewable from the CPCS craft control 406. The site equipment inventorydatabase 408 contains the data identifying the site equipment inventoryand status.

The site craft control 410 provides a graphical interface for viewingand control of call processor alarms. The site craft control 410 isintegrated with call processing applications alarms and other equipmentalarms via management information bases (MIBs) to allow operators of thesystem to have one common view. Each call processor or switch isresponsible for transmitting the MIBs to the CPCS 104.

The regional craft view 412 provides multiple operations centers viewsto multiple call processor or switch sites. When an operations centerfocuses on an individual site, they can view the same data and userinterface screens as call processor or switch site operators. The CPCSequipment inventory database 414 contains the data identifying the callprocessor or switch sites' equipment inventory and status.

FIG. 5 illustrates an exemplary embodiment of an RCC 308 of the presentinvention. The RCC 308 of FIG. 5 has a call trace system 502 with a userauthorize database 504, a call tap system 506 with a call tap deliverydatabase 508, an active call query system 510 with an active call filedatabase 512, a fraud detection system 514 with a connect deny database516, a test call system 518 with a traffic management history database520, and a skip & gap system 522. The call trace system 502, the calltap system 506, the fraud detection system 514, and the test call system518 also can access the active call file database 512.

The call trace system 502 can trace a call from a centralized location,such as the call processor or switch site, while the call is active andin progress. The call trace system 502 uses information from a centralcomputer file in a CPCS 104 for the call trace. Typically, the calltrace system 502 accesses the active call file database 512 to obtainthe call trace information for an active call. In addition, the calltrace system 502 can trace a call for completed calls. The completedcall trace function is implemented by accessing the historical records.

The call trace system 502 verifies the data for the call processingtables directly at the call processor 204 to ensure that the callprocessor and the CPCS 104 are synchronized. (See FIG. 3.) For example,in a first function the call trace system 502 can traverse the callprocessing tables in the CPCS 104 based on data input by an operator. Inanother function a selected set of parameters determines if the callprocessor 204 and the CPCS 104 are synchronized. Automated routinesensure that synchronization and any out of synchronization conditionsare reported as an alarm. In a third function the CIB data can beretrieved for review of SS7 routing information, the interworking unitconnection information, the ATM matrix connection information, and otherdata that is used to determine quality of service on historical calls.

The user authorize database 504 contains information for providingsecurity and secure access to the RCC 308 and its subsystems. Theinformation in the user authorize database 504 identifies operators thatcan trace calls. This function and information make the call tracesystem 502 and its functions highly secure.

The call tap system 506 taps calls that are active in progress. The calltap system 506 can tap every call to or from a location. The call tapsystem 506 is configured to tap the calls from a centralized location,such as from the call processor or switch site. The call tap deliverydatabase 508 contains warrant preset information that allows an operatoror function to tap a call.

The active call query system 510 finds particular calls that are active.The active call query system 510 searches calls that are in progress andobtains details about the call. The active call query system 510 can beused, for example, for call maintenance, such as to fix a call or tocheck the quality of the call, and for law enforcement requirements,such as call tap and call trace. The active call query system 510 can beused from a centralized location, such as a call processor or switchsite. For example, a desktop computer may be used to employ the activecall query system 510 on a network wide basis.

The active call file database 512 contains the history of all the calls,including the call processor or switch, the calling number, the callednumber, the path, the equipment used to connect the calls, and echocanceller data. For example, the CIB file contains the exact number ofthe echo canceller for the call, if used, the exact connections, and theexact signaling links used. Therefore, by querying the active call filedatabase 512, a specific call can be determined and the exactinformation for the call examined to determine loss of quality or otherconcerns for calls. This function is a significant advance over priorsystems that are manual and employ a hit or miss strategy.

The fraud detection system 514 uses data from active calls to determinefraudulent callers. The fraud detection system 514 may force a releaseof the calls while the calls are active. This is an improvement over theart since prior systems require a call to go on-hook before taking anaction. The connect deny database 516 contains records of whichconnections are to be denied. The records of the connections can bebased on automatic number identification (ANI).

The test call system 518 can test calls from locations remote from thecurrent call connection to determine if the quality of the connection isacceptable. For example, the test call system 518 allows the CPCS 104 totest calls at locations that are remote from the CPCS or the callprocessor 204. The test call system 518 provides physical routeverification for calls by locating the CIB of a call that has a poorquality. Because the CIB has data associated with the physical path, thephysical path can be verified. The traffic manage history database 520contains data related to the test history of the call. The results oftest calls, including links to the CIB file and the call signaling, arestored in the traffic manage history database 520.

The skip and gap system 522 uses call throttling features to ensure thatthe ATM and TDM connections and the call signaling links at the callprocessor or switch site are not overloaded. The skip and gap system 522use call control features, such as dropping calls and dropping events,to control traffic.

FIG. 6 illustrates an exemplary embodiment of a performance monitoringsystem which includes an RHDS 310 and a historical data system 312 ofthe present invention. In the embodiment of FIG. 6, the RHDS 310 and thehistorical data system 312 operate in conjunction with each other.

The RHDS 310 has a hardware event database 602, a trunk group eventdatabase 604, an ATM connections database 606, and an SS7 links database608. The historical data system 312 has historical information on ahardware performance system 610, a trunk group system 612, an ATM system614, and an SS7 system 616.

The hardware performance system 610 processes hardware performance datasuch as logs, alarms, and OMs received from the elements of the callprocessing system 102, including the signaling interface 202, the callprocessor 204, the interworking unit 206, and the ATM matrix 208 (seeFIG. 3). The hardware performance data is taken every fifteen minutesand is stored in the hardware event database 602. The hardwareperformance system 610 implements the hardware measures as defined forcomputing platforms.

The hardware performance system 610 analyzes the hardware performancedata to determine operational patterns and to provide causal analysisfor prediction of fault, equipment failure, and other forecasts. Forexample, a single cause code, data for a call processor or switch site,or a specified detail can be reviewed. In addition, an operator can viewthe data in different configurations, such as organized by cause code,call processor or switch, or trunk, and at different levels ofspecificity, such as different increments of time. Because the hardwareperformance data is stored in the hardware event database 602 in athree-dimensional array, an operator can zoom in or zoom out whileviewing the data. For example, data can be viewed by month, day, hour,or five minute increments. Also, the hardware performance system 610summarizes the history at a specified level, such as a five minuteincrement, for trending analysis. Analysis can be provided for a fiveminute history level.

The trunk group system 612 processes informational data such as logs,alarms, and OMs received for all trunk groups. The trunk group data istaken and is stored in the trunk group database 604. The trunk groupsystem 612 analyzes the trunk group data to determine operationalpatterns and to provide causal analysis for prediction of fault,equipment failure, and other forecasts. For example, a single causecode, data for a call processor or switch site, or a specified detailcan be reviewed. In addition, an operator can view the data in differentconfigurations, such as organized by cause code, call processor orswitch, or trunk, and at different levels of specificity, such asdifferent increments of time. Because the trunk group data is stored inthe trunk group event database 604 in a three-dimensional array, anoperator can zoom in or zoom out while viewing the data. For example,data can be viewed by month, day, hour, or five minute increments. Also,the trunk group system 612 summarizes the history at a specified level,such as a five minute increment, for trending analysis. Analysis can beprovided for a five minute history level.

The ATM system 614 processes informational data such as logs, alarms,and OMs received for all ATM connections. The ATM connection data istaken and is stored in the ATM connections database 606. The ATM system614 analyzes the ATM connection data to determine operational patternsand to provide causal analysis for prediction of fault, equipmentfailure, and other forecasts. For example, a single cause code, data fora call processor or switch site, or a specified detail can be reviewed.In addition, an operator can view the data in different configurations,such as organized by cause code, call processor or switch, or trunk, andat different levels of specificity, such as different increments oftime. Because the ATM connection data is stored in the ATM connectionsdatabase 606 in a three-dimensional array, an operator can zoom in orzoom out while viewing the data. For example, data can be viewed bymonth, day, hour, or five minute increments. Also, the ATM system 614summarizes the history at a specified level, such as a five minuteincrement, for trending analysis. Analysis can be provided for a fiveminute history level.

The SS7 system 616 processes informational data such as logs, alarms,and OMs received for all SS7 links, such as for measures of linkutilization and the type of messaging that occurs for the messagetransfer part (MTP) layers and the signaling connection control part(SCCP) layers. The SS7 link data is taken and is stored in the SS7 linksdatabase 608. The SS7 system 616 analyzes the SS7 link data to determineoperational patterns and to provide causal analysis for prediction offault, equipment failure, and other forecasts. For example, a singlecause code, data for a call processor or switch site, or a specifieddetail can be reviewed.

In addition, an operator can view the data in different configurations,such as organized by cause code, call processor or switch, or trunk, andat different levels of specificity, such as different increments oftime. Because the SS7 links data is stored in the SS7 links database 608in a three-dimensional array, an operator can zoom in or zoom out whileviewing the data. For example, data can be viewed by month, day, hour,or fifteen minute increments. Also, the SS7 system 616 summarizes thehistory at a specified level, such as a fifteen minute increment, fortrending analysis. Analysis can be provided for a five minute historylevel.

FIG. 7 illustrates an exemplary embodiment of an accounting system 314of the present invention. The accounting system 314 of FIG. 7 has a gapreport system 702 with a gap event/history database 704, a CIB reportsystem 706 and a CDR report system 708 which have a circuit/call logdatabase 710, a duplicate report system 712 with a duplicateevent/history database 714, and a billing report system 716 with abilling event/history database 718.

The gap report system 702 processes the gap event history contained inthe gap event/history database 704 so that it can be viewed in agraphical output or in a report. Each call processor or switch uniquelyidentifies an ECDB which then is transmitted by the call processor orswitch to the CPCS 104. If the gap report system 702 detects a break inthe sequence on the ECDB sequence number, it will be recorded in the gapevent/history database 704. The gap report system 702 will initiate aprocess so that the CPCS 104 will automatically attempt to recover thelost ECDB record.

The CIB report system 706 processes the CIBs that are stored in thecircuit/call log database 710 to determine the number of each CIB recordtype that was converted from ECDBs that were received from a callprocessor or switch. The CIB data is processed on a call processor orswitch basis and on a fifteen minute basis.

The CDR report system 708 processes the CDRs that are stored in thecircuit/call log database 710 to determine the number of each CIB recordtype that was translated into a billable CDR. The CDR data is processedon a call processor or switch basis and on a per hour basis.

The duplicate report system 712 processes the ECDBs stored in theduplicate event/history 714 to determine if a duplicate record wasgenerated by a call processor or switch. The duplicate record isdetermined based on the ECDB sequence number, the time points, and otherpertinent data in the ECDB. If a duplicate record is found, it isrecorded by the duplicate report system 712, and a report is generated.Duplicate records are recorded in the duplicate event/history database714.

The billing report system 716 processes the ECDBs/CIBs/CDRs to keep ahistorical record of billing events, such as the length of the call, thetime of day for the call, the called party, and others. Events such asexternal accounting system unavailable, wide area network devicesunavailable, and switch clock changes, are recorded in this record. Therecords are recorded in the billing event/history database 718.

FIG. 8 illustrates an exemplary embodiment of the CMS 316 of the presentinvention. The CMS 316 of FIG. 8 has a user security configurationsystem 802 with a user security/authorize database 804, a site equipmentconfiguration system 806 with a site equipment inventory database 808, aservice configuration system 810, a CPCS equipment configuration system812 with a CPCS equipment inventory database 814, and an SS7 linkconfiguration system 816 with an SS7 link inventory database 818.

The user security configuration system 802 is a CPCS centrallycontrolled user security system. The user security configuration system802 provides operators the ability to define objects in the telephonynetworks that can be managed by simple network management protocol(SNMP) or common management information protocol (CMIP) and that canimplement user security at the object level. Although CMIP provides alevel of security that SNMP is not able to provide, some objects do notrequire the higher level of security available through CMIP objects.Thus, both CMIP objects and SNMP objects may be used.

In one example, the system could be configured so that the callprocessing tables are defined as a telephony managed network managedobject, and only selected operators would be given the capacity toupdate them. However, other non-selected operators would be able to onlyview the call processing tables. The user security configuration data isstored in the user security/authorize database 804.

The site equipment configuration system 806 processes the MIBs todetermine the hardware configurations of the call processor or switchsite, including the signaling interface 202, the call processor 204, theinterworking unit 206, and the ATM matrix 208 (see FIG. 3). The hardwareconfiguration data is stored in the site equipment inventory database808, and it is viewable from the CPCS 104 for authorized users (see FIG.3).

The service configuration system 810 allows authorized users a mechanismto view and update the call processing tables. The service configurationsystem 810 maintains an image file for updates made to the callprocessing tables at the CPCS 104. The service configuration system 810allows external accounting systems 320 and legacy systems to retrievethe image data.

The CPCS equipment configuration system 812 processes MIBs to determinethe versions of the hardware and software installed in the callprocessor or switch site, including those for the signaling interface202, the call processor 204, the interworking unit 206, and the ATMmatrix 208 (see FIG. 3). The hardware and software version data isstored in the CPCS equipment inventory database 814, and it is viewablefrom the CPCS 104 for authorized users (see FIG. 3).

The SS7 link configuration system 816 processes MIBs to determine theconfiguration of the SS7 links extending to and from the call processoror switch site. The SS7 link data is stored in the SS7 link inventorydatabase 818, and it is viewable from the CPCS 104 for authorized users(see FIG. 3).

The Controllable ATM Matrix

FIG. 9 illustrates an exemplary embodiment of a controllableasynchronous transfer mode (ATM) matrix (CAM), but other CAMs thatsupport the requirements of the invention also are applicable. The CAM902 may receive and transmit ATM formatted user communications or callsignaling.

The CAM 902 preferably has a control interface 904, a controllable ATMmatrix 906, an optical carrier-M/synchronous transport signal-M(OC-M/STS-M) interface 908, and an OC-X/STS-X interface 910. As usedherein in conjunction with OC or STS, “M” refers to an integer, and “X”refers to an integer.

The control interface 904 receives control messages originating from thesignaling processor 912, identifies virtual connection assignments inthe control messages, and provides these assignments to the matrix 906for implementation. The control messages may be received over an ATMvirtual connection and through either the OC-MISTS-M interface 908 orthe OC-X/STS-X interface 910 through the matrix 906 to the controlinterface 904, through either the OC-M/STS-M interface or the OC-X/STS-Xinterface directly to the control interface, or through the controlinterface from a link.

The matrix 906 is a controllable ATM matrix that provides cross connectfunctionality in response to control messages from the signalingprocessor 912. The matrix 906 has access to virtual path/virtualchannels (VP/VCs) over which it can connect calls. For example, a callcan come in over a VP/VC through the OC-MISTS-M interface 908 and beconnected through the matrix 906 over a VP/VC through the OC-X/STS-Xinterface 910 in response to a control message received, by thesignaling processor 912 through the control interface 904. Alternately,a call can be connected in the opposite direction. In addition, the callcan be received over a VP/VC through the OC-M/STS-M interface 908 or theOC-X/STS-X interface 910 and be connected through the matrix 906 to adifferent VP/VC on the same OC-M/STS-M interface or the same OC-X/STS-Xinterface.

The OC-M/STS-M interface 908 is operational to receive ATM cells fromthe matrix 906 and to transmit the ATM cells over a connection to thecommunication device 914. The OC-M/STS-M interface 908 also may receiveATM cells in the OC or STS format and transmit them to the matrix 906.

The OC-X/STS-X interface 910 is operational to receive ATM cells fromthe matrix 906 and to transmit the ATM cells over a connection to thecommunication device 916. The OC-X/STS-X interface 910 also may receiveATM cells in the OC or STS format and transmit them to the matrix 906.

Call signaling may be received through and transferred from theOC-M/STS-M interface 908. Also, call signaling may be received throughand transferred from the OC-X/STS-X interface 910. The call signalingmay be connected on a connection or transmitted to the control interfacedirectly or via the matrix 906.

The signaling processor 912 is configured to send control messages tothe CAM 902 to implement particular features on particular VP/VCcircuits. Alternatively, lookup tables may be used to implementparticular features for particular VP/VCs.

FIG. 10 illustrates another exemplary embodiment of a CAM which has timedivision multiplex (TDM) capability, but other CAMs that support therequirements of the invention also are applicable. The CAM 1002 mayreceive and transmit in-band and out-of-band signaled calls.

The CAM 1002 preferably has a control interface 1004, an OC-N/STS-Ninterface 1006, a digital signal level 3 (DS3) interface 1008, a DS1interface 1010, a DS0 interface 1012, an ATM adaptation layer (AAL)1014, a controllable ATM matrix 1016, an OC-M/STS-M interface 1018A, anOC-X/STS-X interface 1018B, and an ISDN/GR-303 interface 1020. As usedherein in conjunction with OC or STS, “N” refers to an integer, “M”refers to an integer, and “X” refers to an integer.

The control interface 1004 receives control messages originating fromthe signaling processor 1022, identifies DS0 and virtual connectionassignments in the control messages, and provides these assignments tothe AAL 1014 or the matrix 1016 for implementation. The control messagesmay be received over an ATM virtual connection and through theOC-MISTS-M interface 1018A to the control interface 1004, through theOC-X/STS-X interface 1018B and the matrix 1016 to the control interface,or directly through the control interface from a link.

The OC-N/STS-N interface 1006, the DS3 interface 1008, the DS1 interface1010, the DS0 interface 1012, and the ISDN/GR-303 interface 1020 eachcan receive user communications from a communication device 1024.Likewise, the OC-M/STS-M interface 1018A and the OC-X/STS-X interface1018B can receive user communications from the communication devices1026 and 1028.

The OC-N/STS-N interface 1006 receives OC-N formatted usercommunications and STS-N formatted user communications and converts theuser communications to the DS3 format. The DS3 interface 1008 receivesuser communications in the DS3 format and converts the usercommunications to the DS1 format. The DS3 interface 1008 can receiveDS3s from the OC-N/STS-N interface 1006 or from an external connection.The DS1 interface 1010 receives the user communications in the DS1format and converts the user communications to the DS0 format. The DS1interface 1010 receives DS1s from the DS3 interface 1008 or from anexternal connection. The DS0 interface 1012 receives user communicationsin the DS0 format and provides an interface to the AAL 1014. TheISDN/GR-303 interface 1020 receives user communications in either theISDN format or the GR-303 format and converts the user communications tothe DS0 format. In addition, each interface may transmit usercommunications in like manner to the communication device 1024.

The OC-M/STS-M interface 1018A is operational to receive ATM cells fromthe AAL 1014 or from the matrix 1016 and to transmit the ATM cells overa connection to the communication device 1026. The OC-M/STS-M interface1018A also may receive ATM cells in the OC or STS format and transmitthem to the AAL 1014 or to the matrix 1016.

The OC-X/STS-X interface 1018B is operational to receive ATM cells fromthe AAL 1014 or from the matrix 1016 and to transmit the ATM cells overa connection to the communication device 1028. The OC-X/STS-X interface1018B also may receive ATM cells in the OC or STS format and transmitthem to the AAL 1014 or to the matrix 1016.

Call signaling may be received through and transferred from theOC-N/STS-N interface 1006 and the ISDN/GR-303 interface 1020. Also, callsignaling may be received through and transferred from the OC-M/STS-Minterface 1018A and the OC-X/STS-X interface 1018B. The call signalingmay be connected on a connection or transmitted to the control interfacedirectly or via an interface as explained above.

The AAL 1014 comprises both a convergence sublayer and a segmentationand reassembly (SAR) sublayer. The AAL 1014 obtains the identity of theDS0 and the ATM VP/VC from the control interface 1004. The AAL 1014 isoperational to convert between the DS0 format and the ATM format. AALsare known in the art, and information about AALs is provided byInternational Telecommunications Union (ITU) documents in the series of1.363, which are incorporated herein by reference. For example, ITUdocument 1.363.1 discusses AAL1. An AAL for voice calls is described inU.S. Pat. No. 5,806,553 entitled “Cell Processing for VoiceTransmission,” which is incorporated herein by reference.

Calls with multiple 64 Kilo-bits per second (Kbps) DS0s are known asNx64 calls. If desired, the AAL 1014 can be configured to accept controlmessages through the control interface 1004 for Nx64 calls. The CAM 1002is able to interwork, multiplex, and demultiplex for multiple DS0s. Atechnique for processing VP/VCs is disclosed in U.S. patent applicationSer. No. 08/653,852, which was filed on May 28, 1996, and entitled“Telecommunications System with a Connection Processing System,” andwhich is incorporated herein by reference.

DS0 connections are bi-directional and ATM connections are typicallyuni-directional. As a result, two virtual connections in opposingdirections typically will be required for each DS0. Those skilled in theart will appreciate how this can be accomplished in the context of theinvention. For example, the cross-connect can be provisioned with asecond set of VP/VCs in the opposite direction as the original set ofVP/VCs.

The matrix 1016 is a controllable ATM matrix that provides cross connectfunctionality in response to control messages from the signalingprocessor 1022. The matrix 1016 has access to VP/VCs over which it canconnect calls. For example, a call can come in over a VP/VC through theOC-M/STS-M interface 1018A and be connected through the matrix 1016 overa VP/VC through the OC-X/STS-X interface 1018B in response to a controlmessage received by the signaling processor 1022 through the controlinterface 1004. Alternately, the matrix 1016 may transmit a callreceived over a VP/VC through the OC-M/STS-M interface 1018A to the AAL1014 in response to a control message received by the signalingprocessor 1022 through the control interface 1004. Communications alsomay occur in opposite directions through the various interfaces.

In some embodiments, it may be desirable to incorporate digital signalprocessing capabilities at, for example, the DS0 level. It also may bedesired to apply echo control to selected DS0 circuits. In theseembodiments, a signal processor may be included. The signaling processor1022 is configured to send control messages to the CAM 1002 to implementparticular features on particular DS0 or VP/VC circuits. Alternatively,lookup tables may be used to implement particular features forparticular circuits or VP/VCs.

It will be appreciated from the teachings above for the CAMs and for theteachings below for the ATM interworking units, that the above describedCAMs can be adapted for modification to transmit and receive otherformatted communications such as synchronous transport module (STM) andEuropean level (E) communications. For example, the OC/STS, DS3, DS1,DS0, and ISDN/GR-303 interfaces can be replaced by STMelectrical/optical (E/O), E3, E1, E0, and digital private networksignaling system (DPNSS) interfaces, respectively.

The ATM Interworking Unit

FIG. 11 illustrates an exemplary embodiment of an interworking unitwhich is an ATM interworking unit 1102 suitable for the presentinvention for use with a SONET system. Other interworking units thatsupport the requirements of the invention also are applicable. The ATMinterworking unit 1102 may receive and transmit in-band and out-of-bandcalls.

The ATM interworking unit 1102 preferably has a control interface 1104,an OC-N/STS-N interface 1106, a DS3 interface 1108, a DS1 interface1110, a DS0 interface 1112, a signal processor 1114, an AAL 1116, anOC-M/STS-M interface 1118, and an ISDN/GR-303 interface 1120. As usedherein in conjunction with OC or STS, “N” refers to an integer, and “M”refers to an integer.

The control interface 1104 receives control messages originating fromthe signaling processor 1122, identifies DS0 and virtual connectionassignments in the control messages, and provides these assignments tothe AAL 1116 for implementation. The control messages are received overan ATM virtual connection and through the OC-M/STS-M interface 1118 tothe control interface 1104 or directly through the control interfacefrom a link.

The OC-N/STS-N interface 1106, the DS3 interface 1108, the DS1 interface1110, the DS0 interface 1112, and the ISDN/GR-303 interface 1120 eachcan receive user communications from a communication device 1124.Likewise, the OC-M/STS-M interface 1118 can receive user communicationsfrom a communication device 1126.

The OC-N/STS-N interface 1106 receives OC-N formatted usercommunications and STS-N formatted user communications and demultiplexesthe user communications to the DS3 format. The DS3 interface 1108receives user communications in the DS3 format and demultiplexes theuser communications to the DS1 format. The DS3 interface 1108 canreceive DS3s from the OC-N/STS-N interface 1106 or from an externalconnection. The DS1 interface 1110 receives the user communications inthe DS1 format and demultiplexes the user communications to the DS0format. The DS1 interface 1110 receives DS1s from the DS3 interface 1108or from an external connection. The DS0 interface 1112 receives usercommunications in the DS0 format and provides an interface to the AAL1116. The ISDN/GR-303 interface 1120 receives user communications ineither the ISDN format or the GR-303 format and converts the usercommunications to the DS0 format. In addition, each interface maytransmit user communications in like manner to the communication device1124.

The OC-M/STS-M interface 1118 is operational to receive ATM cells fromthe AAL 1116 and to transmit the ATM cells over the connection to thecommunication device 1126. The OC-M/STS-M interface 1118 also mayreceive ATM cells in the OC or STS format and transmit them to the AAL1116.

Call signaling may be received through and transferred from theOC-N/STS-N interface 1106 and the ISDN/GR-303 interface 1120. Also, callsignaling may be received through and transferred from the OC-M/STS-Minterface 1118. The call signaling may be connected on a connection ortransmitted to the control interface directly or via another interfaceas explained above.

The AAL 1116 comprises both a convergence sublayer and a segmentationand reassembly (SAR) sublayer. The AAL 1116 obtains the identity of theDS0 and the ATM VP/VC from the control interface 1104. The AAL 1116 isoperational to convert between the DS0 format and the ATM format.

If desired, the AAL 1116 can be configured to accept control messagesthrough the control interface 1104 for Nx64 calls. The ATM interworkingunit 1102 is able to interwork, multiplex, and demultiplex for multipleDS0s.

DS0 connections are bi-directional and ATM connections are typicallyuni-directional. As a result, two virtual connections in opposingdirections typically will be required for each DS0. Those skilled in theart will appreciate how this can be accomplished in the context of theinvention. For example, the cross-connect can be provisioned with asecond set of VP/VCs in the opposite direction as the original set ofVP/VCs.

In some embodiments, it may be desirable to incorporate digital signalprocessing capabilities at the DS0 level. It may also be desired toapply echo control to selected DS0 circuits. In these embodiments, asignal processor 1114 is included either separately (as shown) or as apart of the DS0 interface 1112. The signaling processor 1122 isconfigured to send control messages to the ATM interworking unit 1102 toimplement particular features on particular DS0 circuits. Alternatively,lookup tables may be used to implement particular features forparticular circuits or VP/VCs.

FIG. 12 illustrates another exemplary embodiment of an interworking unitwhich is an ATM interworking unit 1202 suitable for the presentinvention for use with an SDH system. The ATM interworking unit 1202preferably has a control interface 1204, an STM-N electrical/optical(E/O) interface 1206, an E3 interface 1208, an E1 interface 1210, an E0interface 1212, a signal processor 1214, an AAL 1216, an STM-Melectrical/optical (E/O) interface 1218, and a DPNSS interface 1220. Asused herein in conjunction with STM, “N” refers to an integer, and “M”refers to an integer.

The control interface 1204 receives control messages from the signalingprocessor 1222, identifies E0 and virtual connection assignments in thecontrol messages, and provides these assignments to the AAL 1216 forimplementation. The control messages are received over an ATM virtualconnection and through the STM-M interface 1218 to the control interface1104 or directly through the control interface from a link.

The STM-N E/O interface 1206, the E3 interface 1208, the E1 interface1210, the E0 interface 1212, and the DPNSS interface 1220 each canreceive user communications from a second communication device 1224.Likewise, the STM-M E/O interface 1218 can receive user communicationsfrom a third communication device 1226.

The STM-N E/O interface 1206 receives STM-N electrical or opticalformatted user communications and converts the user communications fromthe STM-N electrical or STM-N optical format to the E3 format. The E3interface 1208 receives user communications in the E3 format anddemultiplexes the user communications to the E1 format. The E3 interface1208 can receive E3s from the STM-N E/O interface 1206 or from anexternal connection. The E1 interface 1210 receives the usercommunications in the E1 format and demultiplexes the usercommunications to the E0 format. The E1 interface 1210 receives E1 sfrom the STM-N E/O interface 1206 or the E3 interface 1208 or from anexternal connection. The E0 interface 1212 receives user communicationsin the E0 format and provides an interface to the AAL 1216. The DPNSSinterface 1220 receives user communications in the DPNSS format andconverts the user communications to the E0 format. In addition, eachinterface may transmit user communications in a like manner to thecommunication device 1224.

The STM-M E/O interface 1218 is operational to receive ATM cells fromthe AAL 1216 and to transmit the ATM cells over the connection to thecommunication device 1226. The STM-M E/O interface 1218 may also receiveATM cells in the STM-M E/O format and transmit them to the AAL 1216.

Call signaling may be received through and transferred from the STM-NE/O interface 1206 and the DPNSS interface 1220. Also, call signalingmay be received through and transferred from the STM-M E/O interface1218. The call signaling may be connected on a connection or transmittedto the control interface directly or via another interface as explainedabove.

The AAL 1216 comprises both a convergence sublayer and a segmentationand reassembly (SAR) sublayer. The AAL obtains the identity of the E0and the ATM VP/VC from the control interface 1204. The AAL 1216 isoperational to convert between the E0 format and the ATM format, eitherin response to a control instruction or without a control instruction.AAL's are known in the art. If desired, the AAL 1216 can be configuredto receive control messages through the control interface 1204 for Nx64user communications.

E0 connections are bi-directional and ATM connections typically areuni-directional. As a result, two virtual connections in opposingdirections typically will be required for each E0. Those skilled in theart will appreciate how this can be accomplished in the context of theinvention.

In some instances, it may be desirable to incorporate digital signalprocessing capabilities at the E0 level. Also, it may be desirable toapply echo control. In these embodiments, a signal processor 1214 isincluded either separately (as shown) or as a part of the E0 interface1212. The signaling processor 1222 is configured to send controlmessages to the ATM interworking unit 1202 to implement particularfeatures on particular circuits. Alternatively, lookup tables may beused to implement particular features for particular circuits or VP/VCs.

The Signaling Processor

The signaling processor receives and processes telecommunications callsignaling, control messages, and customer data to select connectionsthat establish communication paths for calls. In the preferredembodiment, the signaling processor processes SS7 signaling to selectconnections for a call. An example of call processing in a callprocessor and the associated maintenance that is performed for callprocessing is described in a U.S. patent application Ser. No. 09/026,766entitled “System and Method for Treating a Call for Call Processing,”which is incorporated herein by reference.

In addition to selecting connections, the signaling processor performsmany other functions in the context of call processing. It not only cancontrol routing and select the actual connections, but it also canvalidate callers, control echo cancellers, generate accountinginformation, invoke intelligent network functions, access remotedatabases, manage traffic, and balance network loads. One skilled in theart will appreciate how the signaling processor described below can beadapted to operate in the above embodiments.

FIG. 13 depicts an embodiment of a signaling processor. Other versionsalso are contemplated. In the embodiment of FIG. 13, the signalingprocessor 1302 has a signaling interface 1304, a call processing controlsystem 1306 (CPCS), and a call processor 1308. It will be appreciatedthat the signaling processor 1302 may be constructed as modules in asingle unit or as multiple units.

The signaling interface 1304 is coupled externally to signaling systems—preferably to signaling systems having a message transfer part (MTP),an ISDN user part (ISUP), a signaling connection control part (SCCP), anintelligent network application part (INAP), and a transactioncapabilities application part (TCAP). The signaling interface 1304preferably is a platform that comprises an MTP level 1 1310, an MTPlevel 2 1312, an MTP level 3 1314, an SCCP process 1316, an ISUP process1318, and a TCAP process 1320. The signaling interface 1304 also hasINAP functionality.

The signaling interface 1304 may be linked to a communication device(not shown). For example, the communication device may be an SCP whichis queried by the signaling interface with a TCAP query to obtainadditional call-associated data. The answer message may have additionalinformation parameters that are required to complete call processing.The communication device also may be an STP or other device.

The signaling interface 1304 is operational to transmit, process, andreceive call signaling. The TCAP, SCCP, ISUP, and INAP functionality usethe services of the MTP to transmit and receive the messages.Preferably, the signaling interface 1304 transmits and receives SS7messages for MTP, TCAP, SCCP, and ISUP. Together, this functionality isreferred to as an “SS7 stack,” and it is well known. The softwarerequired by one skilled in the art to configure an SS7 stack iscommercially available. One example is the OMNI SS7 stack from Dale,Gesek, McWilliams & Sheridan, Inc. (the DGM&S company).

The processes of the signaling interface 1304 process information thatis received in message signal units (MSUs) and convert the informationto call information elements that are sent to the call processor 1308 tobe processed. A call information element may be, for example, an ISUPIAM message parameter from the MSU. The signaling interface 1304 stripsthe unneeded header information from the MSU to isolate the messageinformation parameters and passes the parameters to the call processor1308 as the call information elements. Examples of these parameters arethe called number, the calling number, and user service information.Other examples of messages with information elements are an ANM, an ACM,an REL, an RLC, and an INF. In addition, call information elements aretransferred from the call processor 1308 back to the signaling interface1304, and the information elements are reassembled into MSUs andtransferred to a signaling point.

The CPCS 1306 is the above-described management and administrationsystem. As described above, the CPCS 1306 is the user interface andexternal systems interface into the call processor 1308. The CPCS 1306serves as a collection point for call-associated data such as logs,operational measurement data, statistical information, accountinginformation, and other call data. The CPCS 1306 can configure thecall-associated data and/or transmit it to reporting centers.

The CPCS 1306 accepts data, such as the translations, from a source suchas an operations system and updates the data in the tables in the callprocessor 1308. The CPCS 1306 ensures that this data is in the correctformat prior to transferring the data to the call processor 1308. TheCPCS 1306 also provides configuration data to other devices includingthe call processor 1308, the signaling interface 1304, the interworkingunit (not shown), and the controllable ATM matrix (not shown). Inaddition, the CPCS 1306 provides for remote control of call monitoringand call tapping applications from the call processor 1308.

The CPCS 1306 also serves as a collection point for alarms. Alarminformation is transferred to the CPCS 1306. The CPCS 1306 thentransports alarm messages to the required communication device. Forexample, the CPCS 1306 can transport alarms to an operations center.

The CPCS 1306 also has a human-machine interface (HMI). This allows aperson to log onto the CPCS 1306 and manage data tables or review datatables in the CPCS or provide maintenance services.

The call processor 1308 processes call signaling and controls an ATMinterworking unit, such as an ATM interworking multiplexer (mux) thatperforms interworking of DS0s and VP/VCs, and an ATM matrix. However,the call processor 1308 may control other communications devices andconnections in other embodiments.

The call processor 1308 comprises a control platform 1322 and anapplication platform 1324. Each platform 1322 and 1324 is coupled to theother platform.

The control platform 1322 is comprised of various external interfacesincluding an interworking unit interface, a controllable ATM matrix, anecho interface, a resource control interface, a call informationinterface, and an operations interface. The control platform 1322 isexternally coupled to an interworking unit control, a controllable ATMmatrix control, an echo control, a resource control, accounting, andoperations. The interworking unit interface exchanges messages with atleast one interworking unit. These messages comprise DS0 to VP/VCassignments, acknowledgments, and status information. The controllableATM matrix interface exchanges messages with at least one controllableATM matrix. These messages comprise DS0 to VP/VC assignments, VP/VC toVP/VC assignments, acknowledgments, and status information. The echocontrol interface exchanges messages with echo control systems. Messagesexchanged with echo control systems might include instructions to enableor disable echo cancellation on particular DS0s, acknowledgments, andstatus information.

The resource control interface exchanges messages with externalresources. Examples of such resources are devices that implementcontinuity testing, encryption, compression, tonedetection/transmission, voice detection, and voice messaging. Themessages exchanged with resources are instructions to apply the resourceto particular DS0s, acknowledgments, and status information. Forexample, a message may instruct a continuity testing resource to providea loopback or to send and detect a tone for a continuity test.

The call information interface transfers pertinent call information to acall information processing system, such as to the CPCS 1306. Typicalcall information includes accounting information, such as the parties tothe call, time points for the call, and any special features applied tothe call. One skilled in the art will appreciate how to produce thesoftware for the interfaces in the control platform 1322.

The application platform 1324 processes signaling information from thesignaling interface 1304 to select connections. The identity of theselected connections are provided to the control platform 1322 for theinterworking unit interface and/or for the controllable ATM matrixinterface. The application platform 1324 is responsible for validation,translation, routing, call control, exceptions, screening, and errorhandling. In addition to providing the control requirements for theinterworking unit and the controllable ATM matrix, the applicationplatform 1324 also provides requirements for echo control and resourcecontrol to the appropriate interface of the control platform 1322. Inaddition, the application platform 1324 generates signaling informationfor transmission by the signaling interface 1304. The signalinginformation might be for ISUP, INAP, or TCAP messages to externalnetwork elements. Pertinent information for each call is stored in anenhanced circuit data block (ECDB) for the call. The ECDB can be usedfor tracking and accounting the call.

The application platform 1324 preferably operates in general accord withthe Basic Call State Model (BCSM) defined by the ITU. An instance of theBCSM is created to handle each call. The BCSM includes an originatingprocess and a terminating process. The application platform 1324includes a service switching function (SSF) that is used to invoke theservice control function-(SCF). Typically, the SCF is contained in anSCP. The SCF is queried with TCAP or INAP messages that are transportedby the signaling interface 1304 and which are initiated with informationfrom the SSF in the application platform 1324. The originating orterminating processes will access remote databases with intelligentnetwork (IN) functionality via the SSF.

Software requirements for the application platform 1324 can be producedin specification and description language (SDL) defined in ITU-T Z. 100or similar logic or description languages. The SDL can be converted intoC code. A real time case tool such as SDT from Telelogic, Inc. or ObjectTime from Object Time, Inc. can be used. Additional C and C++ code canbe added as required to establish the environment. It will beappreciated that other software languages and tools may be used.

The call processor 1308 can be comprised of the above-described softwareloaded onto a computer. The computer can be a generally availablefault-tolerant Unix computer, such as those provided by Sun, Tandem, orHewlett Packard. It may be desirable to utilize the multi-threadingcapability of a Unix operating system.

From FIG. 13, it can be seen that the application platform 1324processes signaling information to control numerous systems andfacilitate call connections and services. The SS7 signaling is exchangedbetween the call processor 1308 and external components through thesignaling interface 1304, and control information is exchanged withexternal systems through the control platform 1322. Advantageously, thesignaling interface 1304, the CPCS 1306, and the call processor 1308 arenot integrated into a switch central processing unit (CPU) that iscoupled to a switching matrix. Unlike an SCP, the components of thesignaling processor 1302 are capable of processing ISUP messagesindependently of TCAP queries.

SS7 Message Designations

SS7 messages are well known. Designations for various SS7 messagescommonly are used. Those skilled in the art are familiar with thefollowing message designations:

-   -   ACM—Address Complete Message    -   ANM—Answer Message    -   BLO—Blocking    -   BLA—Blocking Acknowledgment    -   CPG—Call Progress    -   CGB—Circuit Group Blocking    -   CGBA—Circuit Group Blocking Acknowledgment    -   GRS—Circuit Group Reset    -   GRA—Circuit Group Reset Acknowledgment    -   CGU—Circuit Group Unblocking    -   CGUA—Circuit Group Unblocking Acknowledgment    -   CQM Circuit Group Query Message    -   CQR—Circuit Group Query Response    -   CRM—Circuit Reservation Message    -   CRA—Circuit Reservation Acknowledgment    -   CVT—Circuit Validation Test    -   CVR—Circuit Validation Response    -   CFN—Confusion    -   COT—Continuity    -   CCR—Continuity Check Request    -   EXM—Exit Message    -   INF—Information    -   INR—Information Request    -   IAM—Initial Address Message    -   LPA—Loop Back Acknowledgment    -   PAM—Pass Along Message    -   REL—Release    -   RLC—Release Complete    -   RSC—Reset Circuit    -   RES—Resume    -   SUS—Suspend    -   UBL—Unblocking    -   UBA—Unblocking Acknowledgment    -   UCIC—Unequipped Circuit Identification Code.        Call Processor Tables

Call processing typically entails two aspects. First, an incoming or“originating” connection is recognized by an originating call process.For example, the initial connection that a call uses to enter a networkis the originating connection in that network. Second, an outgoing or“terminating” connection is selected by a terminating call process. Forexample, the terminating connection is coupled to the originatingconnection in order to extend the call through the network. These twoaspects of call processing are referred to as the originating side ofthe call and the terminating side of the call.

FIG. 14 depicts an exemplary data structure preferably used by the callprocessor 1302 of FIG. 13 to execute the BCSM. This is accomplishedthrough a series of tables that point to one another in various ways.The pointers typically are comprised of next function and next labeldesignations. The next function points to the next table, and the nextlabel points to an entry or a range of entries in that table. It will beappreciated that the pointers for the main call processing areillustrated in FIG. 14.

The primary data structure has a TDM trunk circuit table 1402, an ATMtrunk circuit table 1404, a trunk group table 1406, a carrier table1408, an exception table 1410, an originating line information (OLI)table 1412, an automatic number identification (ANI) table 1414, acalled number screening table 1416, a called number table 1418, arouting table 1420, a trunk group class of service (COS) table 1422, anda message mapping table 1424. Also included in the data structure are aday of year table 1426, a day of week table 1428, a time of day table1430, and a time zone table 1432.

The TDM trunk circuit table 1402 contains information required toprovision the TDM side of a connection from the call processor site.Each circuit on the TDM side of a connection has an entry. The TDM trunkcircuit table 1402 is accessed from the trunk group table 1406 or anexternal call process, and it points to the trunk group table.

The ATM trunk circuit table 1404 contains information required toprovision the ATM side of a connection. Typically, one record appears inthis table per ATM trunk group. Although, the system can be configuredalternately for multiple records per trunk group. The ATM trunk circuittable 1404 is accessed from the trunk group table 1406 or an externalcall process, and it points to the trunk group table.

The trunk group table 1406 contains information that is required tobuild trunk groups out of different trunk members identified in the TDMand ATM trunk circuit tables 1402 and 1404. The trunk group table 1406contains information related to the originating and terminating trunkgroups. The trunk group table 1406 typically points to the carrier table1408. Although, the trunk group table 1406 may point to the exceptiontable 1410, the OLI table 1412, the ANI table 1414, the called numberscreening table 1416, the called number table 1418, the routing table1420, the day of year table 1426, the day of week table 1428, the timeof day table 1430, and the treatment table (see FIG. 15).

For default processing of an IAM of an outgoing call in the forwarddirection, when the call process determines call setup and routingparameters for user communications on the originating portion, the trunkgroup table 1406 is the next table after the TDM and ATM trunk circuittables 1402 and 1404, and the trunk group table points to the carriertable 1408. For default processing of an IAM of an outgoing call in theforward direction, when the call process determines call setup androuting parameters for user communications on the terminating portion,the trunk group table 1406 is the next table after the routing table1420, and the trunk group table points to the TDM or ATM trunk circuittable 1402 or 1404. For default processing of an ACM or an ANM of anoutgoing call in the originating direction, when the call processdetermines parameters for signaling, the trunk group table 1406 is thenext table after the TDM or ATM trunk circuit table 1402 or 1404, andthe trunk group table points to the message mapping table 1424. It willbe appreciated that this is the default method, and, as explainedherein, other implementations of table processing occur.

The carrier table 1408 contains information that allows calls to bescreened based, at least in part, on the carrier information parameterand the carrier selection parameter. The carrier table 1408 typicallypoints to the exception table 1410. Although, the carrier table 1408 maypoint to the OLI table 1412, the ANI table 1414, the called numberscreening table 1416, the called number table 1418, the routing table1420, the day of year table 1426, the day of week table 1428, the timeof day table 1430, the treatment table (see FIG. 15), and the databaseservices table (see FIG. 16).

The exception table 1410 is used to identify various exceptionconditions related to the call that may influence the routing orhandling of the call. The exception table 1410 contains information thatallows calls to be screened based, at least in part, on the called partynumber and the calling party's category. The exception table 1410typically points to the OLI table 1412. Although, the exception table1410 can point to the ANI table 1414, the called number screening table1416, the called number table 1418, the routing table 1420, the day ofyear table 1426, the day of week table 1428, the time of day table 1430,the call rate table, the percent control table, the treatment table (seeFIG. 15), and the database services table (see FIG. 16).

The OLI table 1412 contains information that allows calls to be screenedbased, at least in part, on originating line information in an IAM. TheOLI table 1412 typically points to the ANI table 1414. Although, the OLItable can point to the called number screening table 1416, the callednumber table 1418, the routing table 1420, the day of year table 1426,the day of week table 1428, the time of day table 1430, and thetreatment table (see FIG. 15).

The ANI table 1414 is used to identify any special characteristicsrelated to the caller's number, which is commonly known as automaticnumber identification. The ANI table 1414 is used to screen and validatean incoming ANI. ANI specific requirements such as queuing, echocancellation, time zone, and treatments can be established. The ANItable 1414 typically points to the called number screening table 1416.Although, the ANI table 1414 can point to the called number table 1418,the routing table 1420, the day of year table 1426, the day of weektable 1428, the time of day table 1430, and the treatment table (seeFIG. 15).

The called number screening table 1416 is used to screen called numbers.The called number screening table 1416 determines the disposition of thecalled number and the nature of the called number. The called numberscreening table 1416 is used to provide the trigger detection point(TDP) for an AIN SCP TCAP query. It is used, for example, with the localnumber portability (LNP) feature. The called number screening table caninvoke a TCAP. The called number screening table 1416 typically pointsto the called number table 1418. Although, the called number screeningtable 1416 can point to the routing table 1420, the treatment table, thecall rate table, the percent table (see FIG. 15), and the databaseservices table (see FIG. 16).

The called number table 1418 is used to identify routing requirementsbased on, for example, the called number. This will be the case forstandard calls. The called number table 1418 typically points to therouting table 1410. In addition, the called number table 1426 can beconfigured to alternately point to the day of year table 1426. Thecalled number table 1418 can also point to the treatment table (see FIG.15) and the database services table (see FIG. 16).

The routing table 1420 contains information relating to the routing of acall for various connections. The routing table 1420 typically points tothe treatment table (see FIG. 15). Although, the routing table also canpoint to the trunk group table 1406 and the database services table (seeFIG. 16).

For default processing of an IAM of an outgoing call in the forwarddirection, when the call process determines call setup and routingparameters for user communications, the routing table 1420 is the nexttable after the called number table 1418, and the routing table pointsto the trunk group table 1406. For default processing of an IAM of anoutgoing call in the forward direction, when the call process determinesparameters for signaling, the routing table 1420 is the next table afterthe called number table 1418, and the routing table points to themessage mapping table 1424. It will be appreciated that this is thedefault method, and, as explained herein, other implementations of tableprocessing occur.

The trunk group COS table 422 contains information that allows calls tobe routed differently based on the class of service assigned to theoriginating trunk group and to the terminating trunk group. The trunkgroup COS table can point to the routing table 1420 or the treatmenttable (see FIG. 15).

When the trunk group COS table 1422 is used in processing, after therouting table 1420 and the trunk group table 1406 are processed, thetrunk group table points to the trunk group COS table. The trunk groupCOS table points back to the routing table 1420 for further processing.Processing then continues with the routing table 1420 which points tothe trunk group table 1406, and the trunk group table which points tothe TDM or ATM trunk circuit table 1402 or 1404. It will be appreciatedthat this is the default method, and, as explained herein, otherimplementations of table processing occur.

The message mapping table 1424 is used to provide instructions for theformatting of signaling messages from the call processor. It typicallycan be accessed by the routing table 1420 or the trunk group table 1406and typically determines the format of the outgoing messages leaving thecall processor.

The day of year table 1426 contains information that allows calls to berouted differently based on the day of the year. The day of year tabletypically points to the routing table 1420 and references the time zonetable 1432 for information. The day of year table 1426 also can point tothe called number screening table 1416, the called number table 1418,the routing table 1420, the day of week table 1428, the time of daytable 1430, and the treatment table (see FIG. 15).

The day of week table 1428 contains information that allows calls to berouted differently based on the day of the week. The day of week tabletypically points to the routing table 1420 and references the time zonetable 1432 for information. The day of week table 1428 also can point tothe called number screening table 1416, the called number table 1418,the time of day table 1430, and the treatment table (see FIG. 15).

The time of day table 1430 contains information that allows calls to berouted differently based on the time of the day. The time of day table1430 typically points to the routing table 1420 and references the timezone table 1432 for information. The time of day table 1430 also canpoint to the called number screening table 1416, the called number table1418, and the treatment table (see FIG. 15).

The time zone table 1432 contains information that allows callprocessing to determine if the time associated with the call processingshould be offset based on the time zone or daylight savings time. Thetime zone table 1432 is referenced by, and provides information to, theday of year table 1426, the day of week table 1428, and the time of daytable 1430.

FIG. 15 is an overlay of FIG. 14. The tables from FIG. 14 are present.However, for clarity, the table's pointers have been omitted, and sometables have not been duplicated in FIG. 15. FIG. 15 illustratesadditional tables that can be accessed from the tables of FIG. 14. Theseinclude an outgoing release table 1502, a treatment table 1504, a callrate table 1506, and a percent control table 1508, and time/date tables1510.

The outgoing release table 1502 contains information that allows callprocessing to determine how an outgoing release message is to beformatted. The outgoing release table 1502 typically points to thetreatment table 1506.

The treatment table 1504 identifies various special actions to be takenin the course of call processing. For example, based on the incomingtank group or ANI, different treatments or cause codes are used toconvey problems to the called and calling parties. This typically willresult in the transmission of a release message (REL) and a cause value.The treatment table 1504 typically points to the outgoing release table1502 and the database services table (see FIG. 16).

The call rate table 1506 contains information that is used to controlcall attempts on an attempt per second basis. Preferably, attempts from100 per second to 1 per minute are programmable. The call rate table1506 typically points to the called number screening table 1416, thecalled number table 1418, the routing table 1420, and the treatmenttable 1504.

The percent control table 1508 contains information that is used tocontrol call attempts based upon a percent value of the traffic that isprocessed through call processing. The percent control table 1508typically points to the called number screening table 1416, the callednumber table 1418, the routing table 1420, and the treatment table 1504.

The date/time tables 1510 have been identified in FIG. 14 as the day ofyear table 1426, the day of week table 1428, the time of day table 1426,and the time zone table 1432. They are illustrated in FIG. 15 as asingle location for ease and clarity but need not be so located.

FIG. 16 is an overlay of FIGS. 14-15. The tables from FIGS. 14-15 arepresent. However, for clarity, the table's pointers have been omitted,and some tables have not been duplicated in FIG. 16.

FIG. 16 illustrates additional tables that can be accessed from thetables of FIGS. 14-15 and which are directed to the TCAP and the SCCPmessage processes. These include a database services table 1602, asignaling connection control part (SCCP) table 1604, an intermediatesignaling network identification (ISNI) table 1606, a transactioncapabilities application part (TCAP) table 1608, and an advancedintelligent network (AIN) event parameters table 1610.

The database services table 1602 contains information about the type ofdatabase service requested by call processing. The database servicestable 1602 references and obtains information from the SCCP table 1604and the TCAP table 1608. After the database function is performed, thecall is returned to normal call processing. The database services table1602 points to the called number table 1418.

The SCCP table 1604 contains information and parameters required tobuild an SCCP message. The SCCP table 1604 is referenced by the databaseservices table 1602 and provides information to the database servicestable.

The ISNI table 1606 contains network information that is used forrouting SCCP message to a destination node. The ISNI table 1606 isreferenced by the SCCP table 1604 and provides information to the SCCPtable.

The TCAP table 1608 contains information and parameters required tobuild a TCAP message. The TCAP table 1608 is referenced by the databaseservices table 1602 and provides information to the database servicestable.

The AIN event parameters table 1610 contains information and parametersthat are included in the parameters portion of a TCAP event message. TheAIN event parameters table 1610 is referenced by the TCAP table 1608 andprovides information to the TCAP table.

FIG. 17 is an overlay of FIGS. 14-16. The tables from FIGS. 14-16 arepresent. However, for clarity, the tables have not been duplicated inFIG. 17. FIG. 17 illustrates additional tables that can be used to setupthe call process so that the tables of FIGS. 14-16 may be used. Thesesetup tables 1702 include a site office table 1704, an external echocanceller table 1706, an interworking unit (IWU) table 1708, acontrollable ATM matrix (CAM) interface table 1710, and a controllableATM matrix (CAM) table 1712.

The site office table 1704 contains information which lists office-wideparameters, some of which are information-based and others which affectcall processing. The site office table 1704 provides information to thecall processor or switch during initialization or other setupprocedures, such as population of data or transfer of information to oneor more memory locations for use during call processing.

The external echo canceller 1706 contains information that provides theinterface identifier and the echo canceller type when an external echocanceller is required. The external echo canceller table 1706 providesinformation to the call processor or switch during initialization orother setup procedures, such as population of data or transfer ofinformation to one or more memory locations for use during callprocessing.

The IWU table 1708 contains the internet protocol (IP) identificationnumbers for interfaces to the interworking units at the call processoror switch site. The IWU table 1708 provides information to the callprocessor or switch during initialization or other setup procedures,such as population of data or transfer of information to one or morememory locations for use during call processing.

The CAM interface table 1710 contains information for the logicalinterfaces associated with the CAM. The CAM interface table 1710provides information to the call processor or switch duringinitialization or other setup procedures, such as population of data ortransfer of information to one or more memory locations for use duringcall processing.

The CAM table 1712 contains information associated with the logical andphysical setup properties of the CAM. The CAM table 1712 providesinformation to the call processor or switch during initialization orother setup procedures, such as population of data or transfer ofinformation to one or more memory locations for use during callprocessing.

FIGS. 18-47 depict examples of the various tables described above. Itwill be appreciated that other versions of tables may be used. Inaddition, information from the identified tables may be combined orchanged to form different tables.

FIG. 18 depicts an example of a TDM trunk circuit table. The TDM trunkcircuit table is used to access information about the originatingcircuit for originating circuit call processing. It also is used toprovide information about the terminating circuit for terminatingcircuit call processing. The trunk group number of the circuitassociated with the call is used to enter the table. The group member isthe second entry that is used as a key to identify or fill informationin the table. The group member identifies the member number of the trunkgroup to which the circuit is assigned, and it is used for the circuitselection control.

The table also contains the trunk circuit identification code (TCIC).The TCIC identifies the trunk circuit which is typically a DS0. The echocanceller (EC) label entry identifies the echo canceller, if any, whichis connected to the circuit. The interworking unit (IWU) label and theinterworking unit (IWU) port identify the hardware location and the portnumber, respectively, of the interworking unit. The DS1/E1 label and theDS1/E1 channel denote the DS1 or the E1 and the channel within the DS1or E1, respectively, that contains the circuit. The initial statespecifies the state of the circuit when it is installed. Valid statesinclude blocked if the circuit is installed and blocked from usage,unequipped if the circuit is reserved, and normal if the circuit isinstalled and available from usage.

FIG. 19 depicts an example of an ATM trunk circuit table. The ATM trunkcircuit table is used to access information about the originatingcircuit for originating circuit call processing. It also is used toprovide information about the terminating circuit for terminatingcircuit call processing.

The trunk group number of the circuit associated with the call is usedto enter the table. The group size denotes the number of members in thetrunk group. The starting trunk circuit identification code (TCIC) isthe starting TCIC for the trunk group, and it is used in the routinglabel of an ISUP message. The transmit interface label identifies thehardware location of the virtual path on which the call will betransmitted. The transmit interface label may designate either aninterworking unit interface or a CAM interface for the designated trunkmembers. The transmit virtual path identifier (VPI) is the VP that willbe used on the transmission circuit side of the call. The receiveinterface label identifies the hardware location of the virtual path onwhich the call will be received. The receive interface label maydesignate either an interworking unit interface or a CAM interface forthe designated trunk members. The receive virtual path identifier (VPI)is the VP that will be used on the reception circuit side of the call.The initial state specifies the state of the circuit when it isinstalled. Valid states include blocked if the circuit is installed andblocked from usage, unequipped if the circuit is reserved, and normal ifthe circuit is installed and available from usage.

FIG. 20A depicts an example of a trunk group table. The trunk groupnumber of the trunk group associated with the circuit is used to keyinto the trunk group table. The administration information field is usedfor information purposes concerning the trunk group and typically is notused in call processing. The associated point code is the point code forthe far end switch or call processor to which the trunk group isconnected. The common language location identifier (CLLI) entry is astandardized Bellcore entry for the associated office to which the trunkgroup is connected. The trunk type identifies the type of the trunk inthe trunk group. The trunk type may be a TDM trunk, an ATM trunk fromthe interworking unit, or an ATM trunk from the CAM.

The associated numbering plan area (NPA) contains informationidentifying the switch from which the trunk group is originating or towhich the trunk group is terminating. The associated jurisdictioninformation parameter (JIP) contains information identifying the switchfrom which the trunk group is originating or to which the trunk group isterminating. If an ISUP JIP is received, an outgoing JIP has the samevalue as the received JIP. If an ISUP JIP is not received in an IAM, anda default JIP value is present, then call processing will populate theJIP of the outgoing IAM with the default value from the trunk grouptable. If a JIP is not received, and there is no default JIP value, thenan outgoing JIP is not transmitted.

The time zone label identifies the time zone that should be used whencomputing a local date and a local time for use with a day of yeartable, the day of week table, and the time of day table. The echocanceller information field describes the trunk group echo cancellationrequirements. Valid entries for the echo canceller information includenormal for a trunk group that uses internal echo cancellation, externalfor a trunk group that requires external echo cancellers, and disablefor a trunk group that requires no echo cancellation for any callpassing over the group.

FIG. 20B is a continuation of FIG. 20A for the trunk group table. Thesatellite entry specifies that the trunk group for the circuit isconnected through a satellite. If the trunk group uses too manysatellites, then a call should not use the identified trunk group. Thisfield is used in conjunction with the nature of connection satelliteindicator field from the incoming IAM to determine if the outgoing callcan be connected over this trunk group. The select sequence indicatesthe methodology that will be used to select a connection. Valid entriesfor the select sequence field include the following: most idle, leastidle, ascending, or descending. The interworking unit (IWU) prioritysignifies that outgoing calls will attempt to use a trunk circuit on thesame interworking unit before using a trunk circuit on a differentinterworking unit.

Glare resolution indicates how a glare situation is to be resolved.Glare is the dual seizure of the same circuit. If the glare resolutionentry is set to “even/odd,” the switch or the call processor with thehigher point code value will control the even number TCICs within thetrunk group. The switch or call processor with the lower point codevalue will control the odd number TCICs. If the glare resolution entryis set to “all,” the call processor controls all of the TCICs within thetrunk group: If the glare resolution entry is set to “none,” the callprocessor will have no glare control and will yield to all doubleseizures within the trunk group.

Continuity control indicates whether continuity is to be checked.Continuity for outgoing calls on the originating call processor arecontrolled on a trunk group basis. This field specifies whethercontinuity is not required or whether continuity is required and thefrequency of the required check. The field identifies a percentage ofthe calls that require continuity check.

The reattempt entry specifies how many times the outgoing call will bere-attempted using a different circuit from the same trunk group after acontinuity check failure, a glare, or other connection failure. Theignore local number portability (LNP) information specifies whether ornot the incoming LNP information is ignored. The treatment label is alabel into the treatment table for the trunk group used on the call.Because specific trunk group connections may require specific releasecauses or treatments for a specific customer, this field identifies thetype of treatment that is required. The message mapping label is a labelinto the message mapping table which specifies the backward messageconfiguration that will be used on the trunk group.

FIG. 20C is a continuation of FIG. 20B for the trunk group table. Thequeue entry signifies that the terminating part of the trunk group iscapable of queuing calls originating from a subscriber that called anumber which terminates in this trunk group. The ring no answer entryspecifies whether the trunk group requires ring no answer timing. If theentry is set to 0, the call processing % ill not use the ring no answertiming for calls terminated on the trunk group. A number other than 0specifies the ring no answer timing in seconds for calls terminating onthis trunk group. The voice path cut through entry identifies how andwhen the terminating call's voice path will be cut through on the trunkgroup. The options for this field include the following: connect for acut through in both directions after receipt of an ACM, answer for cutthrough in the backward direction upon receipt of an ACM, then cutthrough in the forward direction upon receipt of an ANM, or immediatefor cut through in both directions immediately after an IAM has beensent.

The originating class of service (COS) label provides a label into aclass of service table that determines how a call is handled based onthe combination of the originating COS and the terminating COS fromanother trunk group. Based on the combination of this field and theterminating COS of another trunk group's field, the call will be handleddifferently. For example, the call may be denied, route advanced, orotherwise processed. The terminating class of service (COS) labelprovides a label into a class of service table that determines how acall is handled based on the combination of the originating COS fromanother trunk group and the terminating COS from the present trunkgroup. Based on a combination of this field and the originating COS thecall will be handled differently. For example, the call may be denied,route advanced, or otherwise processed.

Call control provides an index to a specific trunk group level trafficmanagement control. Valid entries include normal for no control applied,skip control, applied wide area telecommunications service (WATS)reroute functionality, cancel control, reroute control overflow, andreroute immediate control. The next function points to the next table,and the next label points to an entry or a range of entries in thattable.

FIG. 21 depicts an example of a carrier table. The carrier label is thekey to enter the table. The carrier identification (ID) specifies thecarrier to be used by the calling party. The carrier selection entryidentifies how the caller specifies the carrier. For example, itidentifies whether the caller dialed a prefix digit or whether thecaller was pre-subscribed. The carrier selection is used to determinehow the call will be routed. The next function points to the next table,and the next label defines an area in that table for further callprocessing.

FIG. 22 depicts an example of an exception table. The exception label isused as a key to enter the table. The calling party's category entryspecifies how to process a call from an ordinary subscriber, an unknownsubscriber, or a test phone. The called number nature of addressdifferentiates between 0+calls, 1+calls, test calls, local routingnumber (LRN) calls, and international calls. For example, internationalcalls might be routed to a pre-selected international carrier. Thecalled number “digits from” and “digits to” focus further processingunique to a defined range of called numbers. The “digits from” field isa decimal number ranging from 1-15 digits. It can be any length and, iffilled with less than 15 digits, is filled with 0s for the remainingdigits. The “digits to” is a decimal number ranging from 1-15 digits. Itcan be any length and, if filled with less than 15 digits, is filledwith 9s for the remaining digits. The next function and next labelentries point to the next table and the next entry within that table forthe next routing function.

FIG. 23 depicts an example of the originating line information (OLI)table. The OLI label is used as a key to enter the table from a priornext function operation. The originating line information entryspecifies the information digits that are being transmitted from acarrier. Different calls are differentiated based on the informationdigits. For example, the information digits may identify an ordinarysubscriber, a multi-party line, N00 service, prison service, cellularservice, or private pay station. The next function and next labelentries point to the next table and the area within that table for thenext routing function.

FIG. 24 depicts an example of an automatic number identification (ANI)table. The ANI label is used as a key to enter the table from a priornext option. The charge calling party number “digits from” and “digitsto” focus further processing unique to ANI within a given range. Theseentries are looked at to determine if the incoming calling number fallswithin the “digits from” and “digits to” fields. The time zone labelindicates the entry in the time zone table that should be used whencomputing the local date and time. The time zone label overrides thetime zone information from the trunk group table 1406.

The customer information entry specifies further customer information onthe originating side for call process routing. The echo cancellation(EC) information field specifies whether or not to apply echocancellation to the associated ANI. The queue entry identifies whetheror not queuing is available to the calling party if the called party isbusy. Queuing timers determine the length of time that a call can bequeued. The treatment label defines how a call will be treated based oninformation in the treatment table. For example, the treatment label maysend a call to a specific recording based on a dialed number. The nextfunction and next label point to the next table and an area within thattable for further call processing.

FIG. 25 depicts an example of a called number screening table. Thecalled number screening label is used as a key to enter the table. Thecalled number nature of address indicates the type of dialed number, forexample, national versus international. The nature of address entryallows the call process to route a call differently based on the natureof address value provided. The “digits from” and “digits to” entriesfocus further processing unique to a range of called numbers. The“digits from” and “digits to” columns both contain called number digits,such as NPA-NXX ranges, that may contain ported numbers and are checkedfor an LRN. This table serves as the trigger detection point (TDP) foran LNP TCAP when, for example, NPA-NXXs of donor switches that have hadsubscribers port their numbers are data filled in the “digits from” and“digits to” fields. The delete digits field provides the number ofdigits to be deleted from the called number before processing continues.The next function and next label point to the next table and the areawithin that table for further call processing.

FIG. 26 depicts an example of a called number table. The called numberlabel is used as a key to enter the table. The called number nature ofaddress entry indicates the type of dialed number, for example, nationalversus international. The “digits from” and “digits to” entries focusfurther processing unique to a range of numbers, including LRNs. Thenext function and next label point to a next table and the area withinthat table used for further call processing.

FIG. 27 depicts an example of a day of year table. The day of year labelis used as a key to enter the table. The date field indicates the localdate which is applicable to the action to be taken during the processingof this table. The next function and next label identify the table andthe area within that table for further call processing.

FIG. 28 depicts an example of a day of week table. The day of week labelis a key that is used to enter the table. The “day from” field indicatesthe local day of the week on which the action to be taken by this tableline entry is to start. The “day to” field indicates the local day ofthe week on which the action to be taken by this table line entry is toend. The next function and next label identify the next table and thearea within that table for further call processing.

FIG. 29 depicts an example of a time of day table. The time of day labelis used as a key to enter the table from a prior next function. The“time from” entry indicates the local time on which an action to betaken is to start. The “time to” field indicates the local time justbefore which the action to be taken is to stop. The next function andnext label entries identify the next table and the area within thattable for further call processing.

FIG. 30 depicts an example of a time zone table. The time zone label isused as a key to enter the table and to process an entry so that acustomer's local date and time may be computed. The coordinateduniversal time (UTC) indicates a standard offset of this time zone fromthe UTC. The UTC is also known as Greenwich mean time, GMT, or Zulu. TheUTC should be positive for time zones east of Greenwich, such as Europeand Asia, and negative for time zones west of Greenwich, such as NorthAmerica. The daylight savings entry indicates whether daylight savingstime is used during the summer in this time zone.

FIG. 31 depicts an example of a routing table. The routing label is usedas a key to enter the table from a prior next function. The route numberspecifies a route within a route list. Call processing will process theroute choices for a given route label in the order indicated by theroute numbers. The next function and next label identify the next tableand the area within that table for further call processing. The signalroute label is associated with the next action to be taken by callprocessing for this call. The signal route label provides the index toaccess the message mapping label. The signal route label is used inorder to modify parameter data fields in a signaling message that isbeing propagated to a next switch or a next call processor.

FIG. 32 depicts an example of a trunk group class of service (COS)table. The originating trunk COS label and the terminating trunk COSlabel are used as keys to enter the table and define call processing.The next function identifies the next action that will be taken by callprocessing for this call. Valid entries in the next function column maybe continued, treat, route advanced, or routing. Based on these entriescall processing may continue using the current trunk group, send thecalls to treatment, skip the current trunk group and the routing tableand go to the next trunk group on the list, or send the call to adifferent label in the routing table. The next label entry is a pointerthat defines the trunk circuit group that the next function will use toprocess the call. This field is ignored when the next function iscontinued or route advanced.

FIG. 33 depicts an example of a treatment table. The treatment label isa key that is used to enter the table. The treatment label is adesignation in a call process that determines the disposition of thecall. The error/cause label correspond either to internally generatederror conditions and call processing or to incoming release causevalues. For each treatment label, there will be a set of errorconditions and cause values that will be associated with a series oflabels for the call processing error conditions and a series of labelsfor all incoming release message cause values. The next function andnext label point to the next table and the area within that table forfurther call processing.

FIG. 34 depicts an example of an outgoing release table. The outgoingrelease label is used as a key to enter the table for processing. Theoutgoing cause value location identifies the type of network to be used.For example, the location entry may specify a local or remote network ora private, transit, or international network. The coding standardidentifies the standard as an International Telecommunications Union(ITU) standard or an American National Standards Institute (ANSI)standard. The cause value designates error, maintenance, ornon-connection processes.

FIG. 35 depicts an example of a percent control table. The percent labelis used as a key to enter the table. The control percentage specifiesthe percentage of incoming calls that will be affected by the control.The control next function allows attempts for call connection to berouted to another table during call processing. The control next labelpoints to an area within that table for further call processing. Thepassed next function allows only incoming attempts to be routed toanother table. The next label points to an area in that table forfurther call processing.

FIG. 36 depicts an example of a call rate table. The call rate label isused as a key to enter the table. The call rate specifies the number ofcalls that will be passed by the control on or for completion. Callprocessing will use this information to determine if the incoming callnumber falls within this control. The control next function allows ablocked call attempt to be routed to another table. The control nextlabel is a pointer that defines the area in the next table for furthercall processing. The passed next function allows only an incoming callattempt to be rerouted to another table. The passed next function is apointer that defines an area in that table for further call processing.

FIG. 37 depicts an example of a database services table. The databaseservices label is used as a key to enter the table. The service typedetermines the type of logic that is applied when building andresponding to database queries. Service types include local numberportability and N00 number translation. The signaling connection controlpart (SCCP) label identifies a location within an SCCP table for furthercall processing. The transaction capabilities application part (TCAP)label identifies a location within a TCAP table for further processing.The next function identifies the location for the next routing functionbased on information contained in the database services table as well asinformation received from a database query. The next label entryspecifies an area within the table identified in the next function forfurther processing.

FIG. 38A depicts an example of a signaling connection control part(SCCP) table. The SCCP label is used as a key to enter the field. Themessage type entry identifies the type of message that will be sent inthe SCCP message. Message types include Unitdata messages and ExtendedUnitdata messages. The protocol class entry indicates the type ofprotocol class that will be used for the message specified in themessage type field. The protocol class is used for connectionlesstransactions to determine whether messages are discarded or returnedupon an error condition. The message handling field identifies how thedestination call processor or switch is to handle the SCCP message if itis received with errors. This field will designate that the message isto be discarded or returned. The hop counter entry denotes the number ofnodes through which the SCCP message can route before the message isreturned with an error condition. The segmentation entry denotes whetheror not this SCCP message will use segmentation and send more than oneSCCP message to the destination.

FIG. 38B is a continuation of FIG. 38A for the SCCP table. Theintermediate signaling network identification (ISNI) fields allow theSCCP message to traverse different networks in order to reach a desirednode. The ISNI type identifies the type of ISNI message format that willbe used for this SCCP message. The route indicator subfield identifieswhether or not this SCCP message requires a special type of routing togo through other networks. The mark identification subfield identifieswhether or not network identification will be used for this SCCPmessage. The label subfield identifies a unique address into the ISNItable when the route indicator sub-field is set to “constrained” and themark identification subfield is set to “yes.”

FIG. 38C is a continuation of FIG. 38B for the SCCP table. FIG. 38Cidentifies the called party address field and subfields to provideinformation on how to route this SCCP message. The address indicatorsubsystem number (SSN) indicates whether or not a subsystem number willbe included in the called party address. The point code entry indicateswhether or not a point code will be included in the calling partyaddress. The global title indicator subfield identifies whether or not aglobal title translation will be used to route the SCCP message. If aglobal title translation is chosen, this subfield also identifies thetype. The routing indicator subfield identifies the elements that willbe used to route the message. Valid entries include global title andpoint code. The national/international subfield identifies whether theSCCP message will use national or international routing and set up.

The subsystem number field identifies the subsystem number for the SCCPmessage. The point code number indicates the destination point code towhich the SCCP message will be routed. This field will be used forrouting messages that do not require SCCP translation.

The global title translation field allows intermediate nodes totranslate SCCP messages so that the messages can be routed to thecorrect destination with the correct point code. The global titletranslation type entry directs the SCCP message to the correct globaltitle translation function. The encode scheme identifies how the addresstype will be encoded. The number plan subfield identifies the numberingplan that will be sent to the destination node. The address typesubfield will identify which address type to use for address digits andthe SCCP routing through the network.

FIG. 38D is a continuation of FIG. 38C for the SCCP table. FIG. 38Didentifies the calling party address field which contains the routinginformation that the destination database uses to retain the SCCPmessage. The address indicator subsystem number (SSN) indicates whetheror not a subsystem number will be included in the called party address.The point code subfield indicates whether or not a point code will beincluded in the calling party address. The global title indicatorsubfield identifies whether or not global title translation will be usedto route the SCCP message. The routing indicator subfield identifieswhich elements will be used throughout the message. This field mayinclude global title elements or point code elements. Thenational/international subfield identifies whether the SCCP will usenational or international routing and set up.

The subsystem number identifies a subsystem number for the SCCP message.The point code number field indicates the destination point code towhich the SCCP message will be routed. The global title translationsallow the intermediate nodes to translate SCCP messages and to route themessages to the correct destination. The global title translation typedirects the SCCP message to the correct global title translationfunction. The encode scheme identifies how the address type will beencoded. The number plan identifies the number plan that will be sent tothe destination node. The address type subfield identifies the addresstype to use for address digits in the SCCP routing through the network.

FIG. 39 depicts an example of an intermediate signaling networkidentification (ISNI) table. The ISNI table contains a list of networksthat will be used for routing SCCP messages to the destination node. TheISNI label is used as a key to enter the table. The network fields 1-16identify the network number of up to 16 networks that may be used forrouting the SCCP message.

FIG. 40 depicts an example of a transaction capabilities applicationpart (TCAP) table. The TCAP label is used as a key to enter the table.The TCAP type identifies the type of the TCAP that will be constructed.The TCAP types include advanced intelligent network (AIN) anddistributed intelligent network architecture (DINA). The tag classindicates whether the message will use a common or proprietarystructure. The package type field identifies the package type that willbe used in the transaction portion of the TCAP message. The componenttype field identifies the component type that will be used in thecomponent portion of the TCAP message. The message type field identifiesthe type of TCAP message. Message types include variable optionsdepending on whether they are AIN message types or DINA message types.

FIG. 41 depicts an example of an external echo canceller table. The echocanceller type specifies if an external echo canceller is being used onthe circuit and, if so, the type of echo canceller. The echo cancellerlabel points to a location in the controllable ATM matrix table forfurther call processing. The RS-232 address is the address of the RS-232interface that is used to communicate with the external echo canceller.The module entry is the module number of the external echo canceller.

FIG. 42 depicts an example of an interworking unit interface table. Theinterworking unit (IWU) is a key that is used to enter the table. TheIWU identification (ID) identifies which interworking unit is beingaddressed. The internet protocol (IP) sockets 1-4 specify the IP socketaddress of any of the four connections to the interworking unit.

FIG. 43 depicts an example of a controllable ATM matrix (CAM) interfacetable. The CAM interface label is used as a key to enter the table. TheCAM label indicates which CAM contains the interface. The logicalinterface entry specifies a logical interface or port number in the CAM.

FIG. 44 depicts an example of a controllable ATM matrix (CAM) table. TheCAM label is used as a key to enter the table. The CAM type indicatesthe type of CAM control protocol. The CAM address identifies the addressof the CAM.

FIG. 45A depicts an example of a call processor or switch site officetable. The office CLLI name identifies a CLLI of the associated officefor the call processor or switch. The call processor or switch site nodeidentifier (ID) specifies the call processor or switch node identifier.The call processor or switch origination identifier (ID) specifies acall processor or switch origination identifier. The software identifier(ID) specifies a software release identifier. The call processoridentifier (ID) specifies the call processor or switch identifier thatis sent to the inter working units.

FIG. 45B is a continuation of FIG. 45A of the call processor or switchsite office table. The automatic congestion control (ACC) specifieswhether ACC is enabled or disabled. The automatic congestion controllevel (ACL) 1 onset identifies an onset percentage value of a firstbuffer utilization. The ACL 1 abate entry specifies an abatementpercentage of utilization for a first buffer. The ACL 2 onset entryspecifies an onset level for a second buffer. The ACL 2 abate entryspecifies an abatement level percentage of buffer utilization for asecond buffer. The ACL 3 onset entry specifies an onset level percentageof buffer utilization for a third buffer. The ACL 3 abate entryspecifies an abatement level percentage of buffer utilization for athird buffer.

FIG. 45C is a continuation of FIG. 45B for the call processor or switchsite office table. The maximum trunks for the off hook queuing (maxtrunks OHQ) specifies a maximum number of trunk groups that can have theoff hook queuing enabled. The OHQ timer one (TQ1) entry specifies thenumber of milliseconds for the off hook timer number one. The OHQ timertwo (TQ2) entry specifies the number of seconds for the off hook timernumber two. The ring no answer timer specifies the number of seconds forthe ring no answer timer. The billing active entry specifies whetherECDBs are being sent to the call processing control system (CPCS). Thenetwork management (NWM) allow entry identifies whether or not aselective trunk reservation and group control are allowed or disallowed.The billing failure free call entry specifies if a call will not bebilled if the billing process is unavailable. The billing failure freecall will either be enabled for free calls or disabled so that there areno free calls.

FIG. 45D is a continuation of FIG. 45C for the call processor or switchsite office table. The maximum (max) hop counts identifies the number ofcall processor or switch hops that may be made in a single call. Themaximum (max) table lookups identifies the number of table lookups thatmay performed for a single call. This value is used to detect loops inrouting tables.

FIGS. 46A-46B depict an example of an advanced intelligent network (AIN)event parameters table. The AIN event parameters table has two columns.The first identifies the parameters that will be included in theparameters portion of the TCAP event message. The second entry mayinclude information for analysis.

FIG. 47 depicts an example of a message mapping table. This table allowsthe call processor to alter information in outgoing messages. Themessage type field is used as a key to enter the table and representsthe outgoing standard message type. The parameters entry is a pertinentparameter within the outgoing message. The indexes point to variousentries in the trunk group and determine if parameters are passedunchanged, omitted, or modified in the outgoing messages.

Those skilled in the art will appreciate that variations from thespecific embodiments disclosed above are contemplated by the invention.The invention should not be restricted to the above embodiments, butshould be measured by the following claims.

1. A communication system, comprising: a plurality of signalingprocessors, wherein each of the signaling processors includes a callprocessing table and each of the signaling processors is configured toreceive signaling for a call, process the signaling based on the callprocessing table to select an identifier for routing the call, andtransmit a control message identifying the identifier; a plurality ofconnection systems, wherein each of the connection systems is configuredto receive user communications for a call, receive a control messagethat includes an identifier for routing the call, interwork the usercommunications based on the identifier in the control message to controlthe point of interworking, and transmit the user communications thatinclude the identifier for routing the call; and a call processingcontrol system coupled to the signaling processors and configured toreceive call processing data from the signaling processors, process thecall processing data to generate updated call processing tables, andtransmit the updated call processing tables to the signaling processorsto remotely control call processing.
 2. The communication system ofclaim 1 wherein the call processing control system comprises: a humanmachine interface cored to provide an interface for an operator to enterthe call processing data to generate the updated call processing tables.3. The communication system of claim 2, wherein the call processingcontrol system comprises: a user security configuration systemconfigured to allow selected operators to enter the call processing datato generate the undated call processing tables.
 4. The communicationsystem of claim 1, wherein the call processing control system receivesthe call processing data from an operations center.
 5. The communicationsystem of claim 1, wherein the call processing control system comprises:a regional craft view system configured to allow an operations center toview configurations of the signaling processors.
 6. The communicationsystem of claim 1, wherein the call processing tables include a callednumber table.
 7. The communication system of claim 1, wherein the callprocessing tables include a routing table.
 8. The communication systemof claim 1, wherein the call processing tables include an automaticnumber identification table.
 9. The communication system of claim 1,wherein each of the connection systems is configured to interwork theuser communications between non-asynchronous transfer mode (ATM)connections and asynchronous transfer mode (ATM) connections.
 10. Thecommunication system of claim 1, wherein each of the connection systemsis configured to interwork the user communications between time divisionmultiplexed (TDM) connections and asynchronous transfer mode (AIM)connections.
 11. A method of operating a communication system comprisinga plurality of signaling processors, a plurality of connection systems,and a call processing control system, the method comprising: in each ofthe signaling processors, receiving signaling for a call, processing thesignaling based on the call processing table to select an identifier forrouting the call, and transmitting a control message identifying theidentifier; in each of the connection systems, receiving usercommunications for a call, receiving a control message that includes anidentifier for routing the call, interworking the user communicationsbased on the identifier in the control message to control the point ofinterworking, and transmitting the user communications that include theidentifier for routing the call; and in the call processing controlsystem, receiving call processing data from the signaling processors,processing the call processing data to generate updated call processingtables, and transmitting the updated call processing tables to thesignaling processors to remotely control call processing.
 12. The methodof claim 11 wherein the call processing control system further comprisesa human machine interface, the method further comprising: in the humanmachine interface, providing an interface for an operator to enter thecall processing data to generate the updated call processing tables. 13.The method of claim 12, wherein the call processing control systemfurther comprises a user security configuration system the methodfurther comprising: in the user security configuration system, allowingselected operators to enter the call processing data to generate theupdated call processing tables.
 14. The method of claim 11, whereinreceiving the call processing data comprises: receiving the callprocessing data from an operations center.
 15. The method of claim 11wherein the call processing system further comprises a regional craftview system, the method further comprising: in the regional craft viewsystem, allowing an operations center to view configurations of thesignaling processors.
 16. The method of claim 11 wherein the callprocessing tables include a called number table.
 17. The method of claim11 wherein the call processing tables include a routing table.
 18. Themethod of claim 11 wherein the call processing tables include anautomatic number identification table.
 19. The method of claim 11wherein interworking the user communications comprises: interworking theuser communications between non-asynchronous transfer mode (ATM)connections and asynchronous transfer mode (ATM) connections.
 20. Themethod of claim 11 wherein interworking the user communicationscomprises: interworking the user communications between time divisionmultiplexed (TDM) connections and asynchronous transfer mode (ATM)connections.